A collection of powerful custom slash commands to enhance Claude Code productivity and workflow automation.
This repository contains custom slash commands for Claude Code that extend its capabilities with specialized workflows for documentation management, code analysis, and architectural understanding.
Conduct interactive architecture interviews to gather institutional knowledge and build comprehensive documentation for your codebase.
Benefits:
- Capture tribal knowledge before it's lost when team members leave
- Systematic documentation of architectural decisions and patterns
- Interactive process that makes documentation gathering engaging
- Structured approach covering all critical aspects of a codebase
- Progressive documentation that builds comprehensive Claude.md files
What it covers:
- Project structure and organization
- Architectural decisions and patterns
- Technology stack usage and conventions
- Domain knowledge and business rules
- Integration patterns and external dependencies
- Performance considerations and scaling
- Team conventions and best practices
Automatically detect and analyze documentation drift by comparing what's documented against the current state of your codebase.
Benefits:
- Automated drift detection saves hours of manual documentation review
- Identifies critical issues like broken examples and incorrect information
- Prioritized findings help you focus on the most important updates first
- Interactive updates make fixing documentation painless
- Prevents documentation rot by catching issues early
- Maintains developer productivity by ensuring docs stay accurate
What it detects:
- File structure changes not reflected in documentation
- Outdated code patterns and examples
- Technology stack changes and new dependencies
- Architecture evolution not captured in docs
- Business logic changes missing from documentation
- Dead references and broken examples
- Copy the command files to your Claude Code commands directory:
# Copy individual commands
cp interview.md ~/.claude/commands/
cp drift.md ~/.claude/commands/
# Or copy all commands at once
cp *.md ~/.claude/commands/- Restart Claude Code or reload your configuration to activate the commands.
/interviewThe command will guide you through an interactive interview process, asking questions about different aspects of your codebase and progressively building documentation in your Claude.md file.
# Analyze entire project for documentation drift
/drift
# Focus analysis on specific directory
/drift src/componentsThe command will analyze your current documentation against the codebase and provide detailed findings with suggested updates.
- Living documentation that evolves with your code
- Comprehensive coverage of architectural decisions and patterns
- Examples that work because drift detection keeps them current
- Institutional knowledge preservation that survives team changes
- Faster onboarding for new team members with comprehensive docs
- Reduced context switching when documentation is accurate and complete
- Better decision making when architectural history is preserved
- Consistent patterns when conventions are documented and maintained
- Architectural integrity maintained through documented decisions
- Pattern consistency across the codebase
- Technical debt visibility through documentation of constraints and trade-offs
- Evolution tracking to understand how and why code has changed
- Run interviews regularly - Architecture evolves, and documentation should too
- Schedule drift detection - Run
/driftmonthly or before major releases - Involve the team - Use
/interviewas a team activity to capture diverse perspectives - Act on findings - Don't let drift reports sit unaddressed
- Start small - Focus on critical areas first, then expand documentation coverage
Feel free to submit issues, feature requests, or pull requests to improve these commands or add new ones.
MIT License - see LICENSE file for details.