Custom Slash Commands

.claude/
└── commands/
    ├── commit.md
    ├── review.md
    ├── today.md
    └── deploy.md

claude
> /commit
> /review src/
> /today

---
description: Test command
---

Say hello and tell me the current time.

claude
> /hello

---
description: Short description shown in /help
---

Your prompt goes here. This is what Claude executes.

You can use multiple paragraphs.

Include specific instructions, context, or steps.

---
description: Explain a concept simply
---

Explain $ARGUMENTS like I'm 5 years old. Use analogies.

> /eli5 recursion
> /eli5 kubernetes networking

---
description: Generate a commit message and commit
---

Look at the staged changes (git diff --cached).

Write a commit message following conventional commits:
- type(scope): description
- Types: feat, fix, docs, refactor, test, chore
- Keep first line under 72 chars
- Add body if changes are complex

Show me the message first. If I approve, run the commit.

---
description: Review code for issues
---

Review $ARGUMENTS for:
1. Bugs and edge cases
2. Security issues
3. Performance problems
4. Code style violations

Be specific. Show line numbers. Suggest fixes.
Skip praise — only mention problems.

> /review src/auth/login.ts
> /review --staged  # Review staged changes

---
description: Morning briefing
---

Give me my daily briefing:

1. **Calendar** — What's on today? Any prep needed?
2. **Tasks** — What's due? What's overdue?
3. **Yesterday** — Any captured notes or loose ends?
4. **Focus** — What should I prioritize?

Keep it tight. Bullet points. No fluff.

---
description: Deploy to production
---

Run the deployment checklist:

1. Check git status — anything uncommitted?
2. Run tests — all passing?
3. Check current branch — on main?
4. Show recent commits since last tag

If all checks pass, ask me to confirm before running deploy.

Stop immediately if any check fails.

---
description: Run tests and fix failures
---

Run the test suite: $ARGUMENTS

If tests fail:
1. Show which tests failed
2. Analyze the failure reason
3. Propose a fix
4. Ask before applying

If all pass, just say "All tests pass" and show coverage if available.

> /test
> /test src/utils/
> /test --coverage

---
description: Create a pull request
---

Create a PR for the current branch:

1. Show diff against main
2. Generate title from commits (conventional format)
3. Write description:
   - What changed
   - Why
   - Testing done
4. Create PR as draft

Ask me to confirm before creating.

.claude/commands/
├── git/
│   ├── commit.md
│   ├── pr.md
│   └── rebase.md
├── dev/
│   ├── test.md
│   ├── lint.md
│   └── deploy.md
└── daily/
    ├── today.md
    └── weekly.md