Commands Overview

ClaudeKit provides a comprehensive set of slash commands to accelerate your development workflow. Each command is designed for specific tasks and automatically orchestrates the appropriate agents.

Command Categories

Core Development

  • /bootstrap - Initialize new projects with spec-driven development
  • /cook - Develop new features
  • /plan - Create implementation plans
  • /brainstorm - Explore feature feasibility
  • /ask - Ask questions about the codebase
  • /watzup - Get project status and recent changes
  • /scout - Find files across large codebases
  • /test - Run test suite and get results
  • /debug - Investigate and diagnose issues

Bug Fixing

Documentation

Git Operations

Planning

  • /plan:ci - Analyze CI failures and create fix plan
  • /plan:two - Create plan with 2 approaches
  • /plan:cro - Create conversion optimization plan

Design & UI

Content & Marketing

Integrations

Journaling

  • /journal - Write development journal entries

Quick Command Reference

Most Used Commands

# Feature Development
/plan [feature description]      # Plan the feature
/cook [feature description]      # Implement the feature

# Bug Fixing
/fix:fast [simple bug]           # Quick fix
/fix:hard [complex issue]        # Thorough investigation + fix
/fix:ci [github-ci-url]          # Fix CI failures

# Documentation
/docs:init                       # First-time setup
/docs:update                     # After making changes

# Git Workflow
/git:cm                          # Commit changes
/git:cp                          # Commit and push
/git:pr [to-branch]              # Create pull request

# Project Status
/watzup                          # What's the current state?
/ask [question]                  # Ask about codebase

Command Syntax

Basic Syntax

/command [required-argument] [optional-argument]

Examples

# No arguments
/test
/watzup
/docs:init

# Required argument
/cook [add user authentication]
/debug [login button not working]
/ask [how does routing work?]

# Optional arguments
/git:pr                          # PR to default branch
/git:pr [develop]                # PR to develop
/git:pr [main] [feature-branch]  # PR from feature to main

# Multiple arguments
/scout [authentication files] [3]  # Find auth files, use 3 agents

Command Workflows

Starting a New Project

1. /bootstrap [project description]
   # OR
   ck new --kit engineer

2. # Customize requirements through Q&A

3. # System automatically:
   - Researches best practices
   - Creates implementation plan
   - Implements features
   - Generates tests
   - Sets up documentation

Developing a Feature

1. /plan [feature description]
   # Creates detailed implementation plan

2. # Review plan in plans/ directory

3. /cook [implement the feature]
   # Implements based on plan
   # Generates tests
   # Updates docs

4. /test
   # Validates implementation

5. /git:cm
   # Commits with conventional message

Fixing a Bug

# Simple bug (you know the fix)
/fix:fast [typo in validation message]

# Complex bug (needs investigation)
/fix:hard [users can't login after password reset]
# - Uses scout to find related files
# - Analyzes code and logs
# - Researches solutions
# - Creates fix plan
# - Implements fix
# - Tests thoroughly

# CI failure
/fix:ci [https://github.com/user/repo/actions/runs/123]
# - Reads CI logs
# - Identifies failure cause
# - Implements fix
# - Verifies CI passes

Updating Documentation

# After implementing features
/docs:update

# When onboarding new team members
/docs:summarize

# When starting with existing codebase
/docs:init

Command Best Practices

Use the Right Command for the Task

✅ Correct Usage

# Small fixes
/fix:fast [typo in button text]

# Complex issues
/fix:hard [memory leak in websocket connection]

# UI issues with screenshot
/fix:ui [screenshot.png] - button misaligned on mobile

❌ Incorrect Usage

# Don't use fast for complex issues
/fix:fast [entire authentication system broken]

# Don't use hard for simple fixes
/fix:hard [typo in comment]

Provide Clear Descriptions

✅ Clear

/plan [add OAuth2 authentication with Google and GitHub providers]
/cook [implement JWT token refresh with 15-minute expiry]
/debug [API returns 500 error when creating user with empty email]

❌ Vague

/plan [add auth]
/cook [make it work]
/debug [something's broken]

Review Before Committing

# 1. Implement
/cook [add rate limiting]

# 2. Test
/test

# 3. Review changes
git diff

# 4. Commit only if satisfied
/git:cm

Use Sequential Commands for Complex Tasks

# 1. Understand codebase
/ask [how is authentication currently implemented?]

# 2. Plan changes
/plan [migrate from session-based to JWT authentication]

# 3. Review plan
cat plans/latest-plan.md

# 4. Implement
/cook [migrate to JWT authentication]

# 5. Test
/test

# 6. Fix if needed
/fix:test

# 7. Commit
/git:cm

Command Flags and Options

Some commands support flags:

/bootstrap

/bootstrap [project description]              # Interactive Q&A
/bootstrap:auto [detailed description]        # Fully automatic

/git:pr

/git:pr                      # PR to default branch (main)
/git:pr [develop]            # PR to develop branch
/git:pr [main] [feature]     # PR from feature to main

/plan

/plan [feature]              # Single approach
/plan:two [feature]          # Two different approaches

Understanding Command Output

Commands provide structured output:

Planning Commands

planner Agent: Analyzing codebase...

Research Results:
- OAuth2 best practices reviewed
- Existing auth patterns identified
- Security considerations documented

Implementation Plan Created:
📄 plans/oauth-implementation.md

Plan Summary:
1. Install dependencies (passport, passport-google-oauth20)
2. Configure OAuth2 providers
3. Implement callback routes
4. Add session management
5. Generate tests
6. Update documentation

Estimated time: 2-3 hours
Files to create: 5
Files to modify: 3

Next: Review plan, then run /cook

Implementation Commands

Code Agent: Implementing from plan...

Dependencies Installed:
✓ passport (0.6.0)
✓ passport-google-oauth20 (2.0.0)

Files Created:
✓ src/auth/oauth-config.js
✓ src/auth/google-strategy.js
✓ src/routes/auth-callback.js

Tests Generated:
✓ tests/auth/oauth.test.js (15 tests)

Documentation Updated:
✓ docs/api/authentication.md

Implementation complete!

Next: Run /test to validate

Test Commands

tester Agent: Running test suite...

Test Results:
✓ Unit tests: 45 passed
✓ Integration tests: 12 passed
✓ E2E tests: 8 passed

Coverage: 87.3%

All tests passed!

Next: Review changes, then /git:cm

Troubleshooting Commands

Command Not Found

Problem: /command not recognized

Solutions:

  1. Verify you’re in a ClaudeKit project (ls .claude/)
  2. Check command exists (ls .claude/commands/)
  3. Run ck update to get latest commands
  4. Restart Claude Code

Command Fails

Problem: Command errors during execution

Solutions:

  1. Check error message for specific issue
  2. Verify prerequisites (API keys, dependencies)
  3. Review agent logs
  4. Try command with simpler input
  5. Use /debug to investigate

Unexpected Results

Problem: Command doesn’t do what expected

Solutions:

  1. Review command documentation
  2. Check if using correct command for task
  3. Provide more specific description
  4. Review generated plans before implementing
  5. Use feedback to refine

Next Steps

Explore specific command categories:

Or learn about:

Key Takeaway: ClaudeKit commands provide a natural, intuitive interface to powerful agent orchestration, making complex development tasks simple and repeatable.