mkdir -p .claude/commands

1# Fix GitHub Issue
2 
3Fix issue #$ARGUMENTS from GitHub:
41. Read the issue description and comments
52. Locate the relevant code
63. Implement a fix with tests
74. Create commit: "fix: Description (closes #$ARGUMENTS)"

/fix-issue 1234

1your-project/
2└── .claude/
3    └── commands/
4        ├── deploy.md        → /deploy
5        ├── fix-issue.md     → /fix-issue
6        └── git/
7            └── squash.md    → /git/squash

1~/.claude/
2└── commands/
3    ├── standup.md          → /standup
4    ├── eod.md              → /eod
5    └── review-pr.md        → /review-pr

1# Skill Title
2 
3Brief description of what this skill does.
4 
5## Instructions
6 
71. First step Claude should take
82. Second step
93. Third step
10 
11## Output Format
12 
13Describe expected output format here.
14 
15IMPORTANT: Critical instructions here.
16YOU MUST: Required behaviors.
17NEVER: Prohibited actions.

1# Create React Component
2 
3Create a new component named $ARGUMENTS.
4 
51. Create src/components/$ARGUMENTS/$ARGUMENTS.tsx
62. Create src/components/$ARGUMENTS/$ARGUMENTS.test.tsx
73. Create src/components/$ARGUMENTS/index.ts
84. Export from src/components/index.ts

/create-component UserProfile

1# Code Review
2 
3Review the current changes:
4 
51. Run `git diff` to see changes
62. Analyze for:
7   - Logic errors
8   - Security vulnerabilities
9   - Performance issues
10   - Missing tests
113. Provide feedback as:
12 
13## Review Summary
14**Status:** Approved / Needs Changes
15 
16### Issues Found
17- [severity] Issue description (file:line)
18 
19### Suggestions
20- Improvement suggestion
21 
22IMPORTANT: Be specific with line numbers.
23YOU MUST: Explain why something is an issue.

1# Deploy to Production
2 
3Safe deployment workflow:
4 
5## Pre-flight Checks
61. Run `git status` - working directory clean?
72. Run `npm test` - all tests passing?
83. Run `npm run build` - build successful?
9 
10If any check fails, STOP and report.
11 
12## Deploy
131. Run `npm run deploy:prod`
142. Wait for completion
153. Run health checks
16 
17## Verify
181. Check production URL
192. Verify key features work
203. Report success/failure
21 
22IMPORTANT: Get confirmation before deploying.
23NEVER: Deploy if tests are failing.

1# Squash Commits
2 
3Squash the last $ARGUMENTS commits:
4 
51. Show `git log --oneline -10`
62. Confirm the commits to squash
73. Run `git rebase -i HEAD~$ARGUMENTS`
84. Use 'squash' for all but first
95. Edit commit message
106. Show result with `git log --oneline -5`
11 
12IMPORTANT: Confirm before rebasing.
13NEVER: Squash commits already pushed.

1# Branch Cleanup
2 
3Clean up merged branches:
4 
51. List merged branches:
6   `git branch --merged main`
7 
82. For each branch (except main, develop):
9   - Ask for confirmation
10   - Delete with `git branch -d`
11 
123. Prune remote tracking:
13   `git remote prune origin`
14 
154. Report branches deleted
16 
17IMPORTANT: Never delete main or develop.

1# Standup Summary
2 
3Generate standup summary:
4 
51. Check git log for yesterday's commits:
6   `git log --since="yesterday" --author="$(git config user.name)"`
7 
82. Check current branch status
9 
103. Look for any failing tests
11 
124. Generate summary:
13 
14## Standup - [Today's Date]
15 
16### Yesterday
17- [List from commits]
18 
19### Today
20- [Current branch/task]
21 
22### Blockers
23- [Any issues]

1# End of Day
2 
3Wrap up the day:
4 
51. Check for uncommitted changes
62. If changes exist, create WIP commit:
7   `wip: [description of work in progress]`
8 
93. Generate summary:
10 
11## EOD - [Date]
12 
13### Completed
14- [Today's commits]
15 
16### In Progress
17- [WIP items]
18 
19### Tomorrow
20- [Next priorities]

1# Investigate Bug
2 
3Investigate: $ARGUMENTS
4 
5## Understand
61. Parse the bug description
72. Identify expected vs actual behavior
83. List affected components
9 
10## Reproduce
111. Find reproduction steps
122. Locate relevant test files
133. Add logging if needed
14 
15## Analyze
161. Search codebase for related code
172. Check git history for recent changes
183. Identify root cause
19 
20## Report
21 
22### Bug Analysis: [Title]
23 
24**Behavior:** What happens
25**Expected:** What should happen
26**Root Cause:** Technical explanation
27**Files Affected:** List
28**Proposed Fix:** Approach
29**Risk:** Low/Medium/High
30 
31DO NOT fix yet - wait for approval.

1# Create API Endpoint
2 
3Create endpoint for: $ARGUMENTS
4 
5## Our Patterns
6- All inputs validated with Zod
7- All responses use ApiResponse<T>
8- Authentication via middleware
9- Proper error handling
10 
11## Steps
121. Create src/app/api/$ARGUMENTS/route.ts
132. Create request/response schemas
143. Add authentication check
154. Implement business logic
165. Add error handling
176. Create tests in __tests__/
18 
19## Template
20```typescript
21import { NextRequest } from 'next/server'
22import { z } from 'zod'
23import { auth, ApiResponse } from '@/lib'
24 
25const schema = z.object({
26  // Define schema
27})
28 
29export async function GET(req: NextRequest) {
30  const session = await auth()
31  if (!session) return ApiResponse.unauthorized()
32 
33  // Implementation
34  return ApiResponse.success(data)
35}

1 
2---
3 
4## Nested Commands
5 
6Organize related commands in folders:

1 
2**Benefits:**
3- Logical grouping
4- Avoid naming conflicts
5- Easier discovery
6- Team-friendly organization
7 
8---
9 
10## Command Resolution
11 
12When you type `/my-command`, Claude searches:
13 
14<Diagram title="Resolution Order" type="flowchart">
15{`flowchart TB
16    A["/my-command"] --> B{Built-in?}
17    B -->|Yes| C[Execute built-in]
18    B -->|No| D{Project skill?}
19    D -->|Yes| E[.claude/commands/my-command.md]
20    D -->|No| F{User skill?}
21    F -->|Yes| G[~/.claude/commands/my-command.md]
22    F -->|No| H[Command not found]
23`}
24</Diagram>
25 
26**Priority:**
271. Built-in commands (highest)
282. Project commands (`.claude/commands/`)
293. User commands (`~/.claude/commands/`)
30 
31<Callout type="warning" title="Name Conflicts">
32Don't name custom commands the same as built-ins. Built-ins always win.
33</Callout>
34 
35---
36 
37## Best Practices
38 
39### 1. Use Descriptive Sections
40 
41```markdown
42# Create Database Migration
43 
44## What This Does
45Creates a timestamped migration file...
46 
47## Prerequisites
48- Database connection configured
49- Prisma schema updated
50 
51## Steps
521. Generate migration
532. Review SQL
543. Apply migration

1## Safety Checks
2 
3Before proceeding:
4- Verify not on production database
5- Confirm backup exists
6- Check no active transactions
7 
8IMPORTANT: If any check fails, STOP.

## Output Format

1## Error Handling
2 
3If migration fails:
41. Do NOT retry automatically
52. Report exact error
63. Suggest causes:
7   - Schema syntax error
8   - Conflicting migration
9   - Connection issue
104. Provide recovery steps

1# Test Skill
2 
3This skill verifies custom commands work.
4 
5Arguments received: $ARGUMENTS
6 
7If you see this, skills are working!
8 
9Respond with:
101. Confirmation you read this
112. The arguments received
123. Current directory

/test-skill hello world

git add .claude/commands/
git commit -m "feat: add team workflow skills"
git push

## Custom Commands
 
This project includes Claude Code skills. See `.claude/commands/` for details.

Error: Unknown command /my-skill

1# Wrong
2Process the input: [user input here]
3 
4# Correct
5Process the input: $ARGUMENTS

1# Before (vague)
2Fix the issue.
3 
4# After (specific)
51. Read the issue description
62. Locate the problematic code
73. Propose a fix and wait for approval
84. Implement only after approval

1# Skill Name
2 
3Brief description.
4 
5## Instructions
6 
71. Step one
82. Step two
93. Step three
10 
11## Output Format
12 
13Expected output format.
14 
15IMPORTANT: Critical rule.
16YOU MUST: Required behavior.
17NEVER: Prohibited action.