qodex-ai/ai-agent-skills/directive-synthesis

Let me help you create a Claude Code slash command! I need a few details:
 
1. **Command name** (lowercase-with-hyphens):
   Example: deploy, review-pr, commit, analyze-tokens
   This will be invoked as: /your-command-name
 
2. **What does this command do?**
   Describe the workflow in 1-2 sentences.
 
3. **Does it need arguments?**
   - None (simple prompt)
   - All arguments: $ARGUMENTS
   - Positional: $1, $2, $3, etc.
 
4. **Does it need bash execution?**
   Commands that run before the slash command (e.g., !`git status`)
 
5. **Scope:**
   - Personal (`~/.claude/commands/`) - just for you
   - Project (`.claude/commands/`) - shared with team
 
6. **Namespace/subdirectory?**
   Example: git/, deploy/, testing/
   Helps organize related commands

Analyze this code for performance issues and suggest optimizations.

---
argument-hint: [file-path]
description: Analyze file for performance issues
---
 
Analyze the file at $1 for performance issues and suggest optimizations.

---
allowed-tools: Bash(git status:*), Bash(git diff:*)
description: Create a git commit
---
 
## Current State
 
-Git status: !`git status`
-Staged changes: !`git diff --staged`
-Recent commits: !`git log --oneline -5`
 
## Your Task
 
Based on the above changes, create a git commit with a clear, conventional commit message.

---
allowed-tools: Bash(npm run:*), Bash(git add:*), Bash(git commit:*)
argument-hint: [component-name]
description: Create a new React component with tests
model: sonnet
---
 
# Create React Component
 
Component name: $1
 
Execute the following workflow:
 
1.**Validate Input**
   !`test -n "$1" && echo "Creating component: $1" || echo "Error: Component name required"`
 
2.**Check Existing Files**
   !`ls src/components/$1.tsx 2>/dev/null || echo "Component does not exist"`
 
3.**Create Files**
   Create the following files:
   -`src/components/$1.tsx`
   -`src/components/$1.test.tsx`
   -`src/components/$1.module.css`
 
4.**Run Tests**
   After creation, run: !`npm run test -- $1`

Brief description of what the command does.
 
[Prompt instructions for Claude]

---
argument-hint: [arg1] [arg2]
description: Brief description shown in /help
allowed-tools: Bash(command:*), Read, Write
model: sonnet
disable-model-invocation: false
---
 
# Command Name
 
Usage: /command-name [args]
 
[Detailed instructions]

Execute the following workflow:
 
1.**Step Name**
   ```bash
   # Bash command (if needed)
   command arg1 arg2
   ```
   -What this step does
   -Validation checks
   -Error handling
 
2.**Next Step**
   [Instructions for Claude]
   -What to check
   -How to proceed
   -What to output
 
3.**Final Step**
   -Summary of results
   -Next actions for user
   -Success criteria

Fix issue #$ARGUMENTS following our coding standards.

Review PR #$1 with priority $2 and assign to $3.
Focus on: $4

---
argument-hint: [environment] [branch]
---
 
Deploy to environment: ${1:-staging}
From branch: ${2:-main}

---
allowed-tools: Bash(git:*)
---
 
## Context
 
-Current branch: !`git branch --show-current`
-Status: !`git status --short`
-Recent commits: !`git log --oneline -5`
 
## Your Task
 
[Instructions based on the above context]

Review the implementation in @src/utils/helpers.js
 
Compare @src/old-version.js with @src/new-version.js
 
Analyze all files in @src/components/

Carefully analyze the following code and think through...
 
Let's approach this step by step...
 
Consider all edge cases before implementing...

~/.claude/commands/command-name.md
~/.claude/commands/category/command-name.md  # With namespace

.claude/commands/command-name.md
.claude/commands/category/command-name.md  # With namespace

To test your command:
1. Restart Claude Code or start a new session
2. Type: /help
3. Find your command in the list
4. Try: /your-command-name [args]
5. Verify it behaves as expected

# No arguments
/your-command
 
# With arguments
/your-command arg1
/your-command arg1 arg2
 
# Edge cases
/your-command ""
/your-command "with spaces"

---
allowed-tools: Bash(git add:*), Bash(git commit:*), Bash(git push:*)
---

Run tests for: $ARGUMENTS

Deploy $1 to $2 environment with tag $3

---
argument-hint: <file> [rest of args]
---
 
Analyze file $1 for: $ARGUMENTS

Analyze file $1 for: ${2:+${@:2}}

Environment: ${1:-production}
Verbose: ${2:-false}

---
allowed-tools: Bash(git:*)
description: Create conventional commit
---
 
## Context
-Status: !`git status --short`
-Diff: !`git diff HEAD`
 
Create a conventional commit message.

---
argument-hint: [component-name]
description: Generate React component
---
 
Create a new React component named $1:
-Component file
-Test file
-Storybook story

---
argument-hint: [file-path]
description: Analyze code complexity
---
 
Analyze @$1 for:
-Cyclomatic complexity
-Code smells
-Improvement suggestions

---
allowed-tools: Bash(npm:*), Bash(git:*)
argument-hint: [environment]
description: Deploy to environment
---
 
Deploy to ${1:-staging}:
1.Run tests: !`npm test`
2.Build: !`npm run build`
3.Deploy: !`npm run deploy:$1`

---
argument-hint: [file-pattern]
description: Generate API documentation
---
 
Generate documentation for: $1
Include:
-Function signatures
-Parameters
-Return types
-Examples

# Convert to TOON
 
Convert the specified JSON file to TOON v2.0 format with automatic optimization and show token savings.
 
Usage: /convert-to-toon <file>

---
allowed-tools: Bash(jq:*), Bash(.claude/utils/toon/zig-out/bin/toon:*)
argument-hint: <file> [--delimiter comma|tab|pipe]
description: Convert JSON to TOON format
---
 
# Convert to TOON
 
File: $1
Delimiter: ${2:-comma}
 
1.**Validate**: !`test -f "$1" && jq empty "$1" 2>&1`
2.**Analyze**: !`jq 'if type == "array" then length else 0 end' "$1"`
3.**Convert**: !`.claude/utils/toon/zig-out/bin/toon encode "$1"`
4.Show savings comparison

# List all commands
ls ~/.claude/commands/*.md
ls .claude/commands/*.md
 
# Verify filename
ls .claude/commands/your-command.md

Debug: $ARGUMENTS
Debug $1: "$1"
Debug $2: "$2"