Template

Files

lmiranda b5d36865ee feat(plugins): add Visual Output headers to all other plugin commands

Add single-line visual headers to 66 command files across 10 plugins:
- clarity-assist (2 commands): 💬
- claude-config-maintainer (5 commands): ⚙️
- cmdb-assistant (11 commands): 🖥️
- code-sentinel (3 commands): 🔒
- contract-validator (5 commands): ✅
- data-platform (10 commands): 📊
- doc-guardian (5 commands): 📝
- git-flow (8 commands): 🔀
- pr-review (7 commands): 🔍
- viz-platform (10 commands): 🎨

Each command now displays a consistent header at execution start:
┌────────────────────────────────────────────────────────────────┐
│  [icon] PLUGIN-NAME · Command Description                       │
└────────────────────────────────────────────────────────────────┘

Addresses #275 (other plugin commands visual output)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-28 17:24:49 -05:00

2.2 KiB

Raw Blame History

/branch-start - Start New Branch

Visual Output

When executing this command, display the plugin header:

┌──────────────────────────────────────────────────────────────────┐
│  🔀 GIT-FLOW · Branch Start                                      │
└──────────────────────────────────────────────────────────────────┘

Then proceed with the workflow.

Purpose

Create a new feature/fix/chore branch with consistent naming conventions.

Usage

/branch-start [description]

Behavior

Step 1: Determine Branch Type

What type of change is this?
1. feat - New feature
2. fix - Bug fix
3. chore - Maintenance task
4. docs - Documentation
5. refactor - Code refactoring

Step 2: Get Description

If not provided, ask:

Brief description (2-4 words):
> add user authentication

Step 3: Generate Branch Name

Convert to kebab-case:

feat/add-user-authentication
fix/login-timeout-error
chore/update-dependencies

Step 4: Create Branch

# Ensure base branch is up-to-date
git checkout <base-branch>
git pull origin <base-branch>

# Create and switch to new branch
git checkout -b <new-branch>

Step 5: Confirm

Created branch: feat/add-user-authentication
Based on: development (abc1234)

Ready to start coding!

Environment Variables

Variable	Default	Description
`GIT_DEFAULT_BASE`	`development`	Branch to create from
`GIT_BRANCH_PREFIX`	`true`	Use type/ prefix

Naming Rules

Lowercase only
Hyphens for spaces
No special characters
Max 50 characters

Validation

Branch name validation:
✓ Lowercase
✓ Valid prefix (feat/)
✓ Descriptive (3+ words recommended)
✗ Too long (52 chars, max 50)

Suggested: feat/add-user-auth
Use this instead? (y/n)

Output

On success:

Branch: feat/add-user-authentication
Base: development @ abc1234
Status: Ready for development

2.2 KiB Raw Blame History