Error analysis and issue diagnosis
Detailed documentation for each command including when to use it, what it's best for, and real-world examples.
Debug and analyze issues
Analyzes error messages, stack traces, and code behavior to identify root causes. Examines logs, state, and execution flow to provide detailed diagnostics and solution suggestions.
/siftcoder:debug <issue>issueError message, stack trace, or issue descriptionInvestigating bugs, analyzing errors, understanding unexpected behavior
Complex bugs, intermittent issues, performance problems
/siftcoder:debug 'TypeError: Cannot read property of undefined' # Analyzes: Stack trace, variable states, execution flow # Provides: Root cause, fix suggestions
Safely investigate codebase
Read-only exploration of codebase to understand behavior, find bugs, or analyze dependencies. Safe to use anywhere as it never modifies files. Perfect for understanding unfamiliar code.
/siftcoder:investigate <query>queryQuestion about code behavior or issue to investigateUnderstanding code, investigating issues without risk, exploring unfamiliar codebases
Legacy code investigation, onboarding, root cause analysis
/siftcoder:investigate 'How does user authentication work?' # Explores: Auth flow, token handling, middleware, validation # Safe: Read-only, no modifications