Command Development

Review this code for security vulnerabilities including:
- SQL injection
- XSS attacks
- Authentication issues

Provide specific line numbers and severity ratings.

This command will review your code for security issues.
You'll receive a report with vulnerability details.

mkdir -p .claude/commands

.claude/commands/
├── review.md           # /review command
├── test.md             # /test command
└── deploy.md           # /deploy command

Review this code for security vulnerabilities including:
- SQL injection
- XSS attacks
- Authentication bypass
- Insecure data handling

Provide specific file:line references for each issue.

---
description: Review code for security vulnerabilities
argument-hint: [file-path]
allowed-tools: ["Read", "Grep", "TodoWrite"]
---

Review the code for security vulnerabilities.

If $ARGUMENTS is provided, focus on that file.
Otherwise, review recent changes.

description: Review code for security vulnerabilities

argument-hint: [file-path]
argument-hint: <required-arg> [optional-arg]
argument-hint: [--flag]

allowed-tools: ["Read", "Write", "Grep", "Bash"]

---
description: Greet the user
argument-hint: [name]
---

If $ARGUMENTS is provided, greet that person by name.
Otherwise, just say "Hello!"

/greet Alice
# Claude will greet Alice

/greet
# Claude will say "Hello!"

---
argument-hint: [file-path]
---

If $ARGUMENTS is provided:
1. Read that specific file
2. Analyze just that file

If $ARGUMENTS is empty:
1. List all changed files with git status
2. Ask which file to analyze
3. Proceed with user's choice

---
description: Deploy application with environment selection
---

Use AskUserQuestion tool to ask:

Header: "Select deployment environment"
Options:
- "Production" (value: "prod")
- "Staging" (value: "stage")
- "Development" (value: "dev")

Based on the selection:
1. Run appropriate deployment script
2. Show deployment progress
3. Verify deployment succeeded

---
description: Create new feature with guided setup
---

Follow these steps:

1. Ask for feature name using AskUserQuestion
2. Create feature branch: feature/[name]
3. Create directory structure
4. Generate boilerplate files
5. Show summary of what was created

---
description: Review recent git changes
---

1. Run `git log --oneline -10` to see recent commits
2. Run `git diff HEAD~1` to see latest changes
3. Analyze the changes for:
   - Code quality issues
   - Potential bugs
   - Best practice violations

---
description: Analyze test coverage
---

First, check if coverage report exists:
```bash
if [ -f coverage/index.html ]; then
  echo "Coverage report found"
else
  echo "Run tests to generate coverage first"
  exit 1
fi

## Command Organization

### Naming Conventions

**Use kebab-case for filenames:**
- `code-review.md` → `/code-review`
- `run-tests.md` → `/run-tests`
- `create-migration.md` → `/create-migration`

### Grouping Related Commands

**Subdirectories for organization:**

### Namespacing

Use prefixes for plugin commands:

Invoked as: `/plugin-name:setup`

## Examples

### Code Review Command

`commands/review.md`:
```markdown
---
description: Review code for quality and best practices
argument-hint: [file-or-directory]
allowed-tools: ["Read", "Grep", "Bash"]
---

Perform a thorough code review.

If $ARGUMENTS is provided, focus on that file or directory.
Otherwise, review git diff of staged changes.

Check for:
1. **Code Quality**
   - Readability and maintainability
   - Proper error handling
   - Edge cases covered

2. **Best Practices**
   - Follows project conventions (check CLAUDE.md)
   - Appropriate abstractions
   - No code duplication

3. **Potential Bugs**
   - Logic errors
   - Race conditions
   - Resource leaks

Provide specific file:line references for each issue.
Rate severity: Critical, High, Medium, Low.

---
description: Run tests with optional filters
argument-hint: [test-pattern]
---

Run the project's test suite.

Steps:
1. Determine test framework (Jest, pytest, etc.)
2. If $ARGUMENTS provided, filter tests by pattern
3. Run tests with appropriate command
4. Analyze failures if any
5. Suggest fixes for failing tests

---
description: Deploy application to specified environment
---

Deploy the application using interactive environment selection.

1. Use AskUserQuestion to select environment:
   - Production (requires confirmation)
   - Staging
   - Development

2. If Production selected, ask for additional confirmation

3. Run pre-deployment checks:
   - Tests passing
   - No uncommitted changes
   - On correct branch

4. Execute deployment:
   - Build application
   - Run deployment script
   - Verify deployment

5. Show deployment summary with URLs

# Load plugin locally
cc --plugin-dir /path/to/plugin

# Try your command
/your-command
/your-command with arguments

/help