
Analyzes code comments for accuracy, completeness, and long-term maintainability. Identifies misleading comments, comment rot, and documentation gaps. Triggers: After adding documentation, before finalizing a PR, when reviewing comments. Examples: - "Check if the comments are accurate" -> verifies comments match code behavior - "Review the documentation I added" -> analyzes new comments for quality - "Analyze comments for technical debt" -> finds outdated or misleading comments - "Are my docstrings correct?" -> validates documentation accuracy
Use this agent when code has been written or modified and needs to be simplified for clarity, consistency, and maintainability while preserving all functionality. This agent should be triggered automatically after completing a coding task or writing a logical chunk of code. It simplifies code by following project best practices while retaining all functionality. The agent focuses only on recently modified code unless instructed otherwise. Triggers: After writing or modifying code, when code needs simplification, when refactoring for clarity. Examples: - "Simplify this code" -> analyzes and simplifies recently modified code - "Make this clearer" -> improves readability while preserving behavior - "Refine this implementation" -> applies project standards and reduces complexity - "Clean up the code I just wrote" -> simplifies recent changes
Identifies silent failures, inadequate error handling, and inappropriate fallback behavior in code. Zero tolerance for errors that occur without proper logging and user feedback. Triggers: When reviewing error handling, checking for silent failures, analyzing catch blocks. Examples: - "Review the error handling" -> audits all error handling in recent changes - "Check for silent failures" -> hunts for swallowed errors and empty catch blocks - "Analyze catch blocks in this PR" -> reviews every try-catch for adequacy - "Are there any hidden failures?" -> finds errors that get silently ignored
Analyzes type design quality focusing on encapsulation, invariant expression, usefulness, and enforcement. Provides quantitative ratings (1-10) for each dimension. Triggers: When adding new types, reviewing type design in PRs, refactoring types. Examples: - "Review the UserAccount type design" -> analyzes type encapsulation and invariants - "Analyze type design in this PR" -> reviews all newly added types - "Check if this type has strong invariants" -> evaluates invariant enforcement - "How can I improve this type?" -> provides actionable type design suggestions
Fix all comments from the GitHub pull request for the current branch. Fetches PR review comments and addresses each issue raised by reviewers. Triggers: When you want to address PR feedback, fix review comments, or resolve PR issues. Examples: - "Fix the PR comments" → fetches and fixes all outstanding review comments - "Address the review feedback" → same behavior - "Fix PR issues" → same behavior
Use this skill when implementing web features to ensure modern APIs and techniques are used. Triggers: Building UI components, adding browser APIs, implementing features that could use legacy patterns. Examples: - "Add a copy to clipboard button" → ensures Clipboard API is used, not document.execCommand - "Implement drag and drop" → ensures HTML Drag and Drop API, not legacy jQuery UI - "Add form validation" → ensures Constraint Validation API, not manual validation - "Fetch data from API" → ensures fetch() with modern patterns, not XMLHttpRequest Additionally, always check for documented browser support requirements before recommending APIs. If you are asked about web development best practices or modern APIs, use this skill to provide up-to-date guidance.
Review and fix PR review bot findings on current PR, loop until resolved. Fetches unanswered bot comments, evaluates each finding, fixes real bugs, dismisses false positives, and replies to every comment with the outcome.
Expert code reviewer that checks code against project guidelines in CLAUDE.md with high precision to minimize false positives. Reviews for bugs, style violations, and code quality. Triggers: Before committing code, when reviewing changes, when checking code quality. Examples: - "Review my recent changes" -> reviews unstaged git diff against project guidelines - "Check if everything looks good" -> comprehensive code review - "Review this code before I commit" -> pre-commit quality check - "Check this PR" -> reviews all changes in the current PR
Analyzes pull request test coverage quality and completeness. Focuses on behavioral coverage rather than line coverage, identifying critical gaps, test quality issues, and missing edge cases. Triggers: After writing tests, before creating a PR, when reviewing test coverage. Examples: - "Check if the tests are thorough" -> analyzes test coverage quality - "Review test coverage for this PR" -> maps tests to changed code - "Are there any critical test gaps?" -> identifies missing test scenarios - "Review my test quality" -> evaluates test resilience and patterns