Reviews code for adherence to coding standards, best practices, and style guidelines. PROACTIVELY use after completing any significant code changes (new features, refactors, bug fixes). Auto-invoke when code is ready for review before committing.
Systematically analyzes errors, stack traces, and logs to identify root causes. PROACTIVELY use when user reports bugs, errors, crashes, or unexpected behavior. Auto-invoke when stack traces or error messages appear in conversation.
Researches official documentation, latest best practices, and current tech stack information. PROACTIVELY use when evaluating libraries, checking API usage, or when implementation involves unfamiliar frameworks. Auto-invoke before using any library/API features from training data.
Assists with Git operations following branching strategy and commit conventions. PROACTIVELY use when creating branches, making commits, resolving conflicts, or managing git workflows. Auto-invoke for any git-related questions or operations.
Analyzes and optimizes code performance. PROACTIVELY use when user mentions slow, laggy, timeout, memory issues, or optimization needs. Auto-invoke when performance-critical code is being written (loops, data processing, API calls).
Safely refactors code while maintaining behavior. PROACTIVELY use when user asks to restructure, extract, rename, or clean up code. Auto-invoke when code smells are detected (duplication, long functions, poor organization).
Clarifies vague requirements by asking probing questions, identifying edge cases, and creating comprehensive specifications. PROACTIVELY use when requirements are vague, ambiguous, or incomplete. Auto-invoke before implementing features that lack clear acceptance criteria.