Skills matching the name, description or GitHub author.
Code review best practices for Python projects. Use when reviewing code, PRs, or diffs. Triggers on "review", "code review", "PR", "pull request", "diff", "check this", "look at this code", "quality", "refactor...
Use when reviewing code, PRs, or diffs. Triggers on "review", "code review", "PR", "pull request", "diff", "check this", "look at this code", "quality", "refactor", "egregious", "cross-file", "duplicate", "dupl...
Address PR feedback with iterative refinement. MUST BE USED when fixing PR issues. Supports auto-detection (CI failures, code review) and manual triage (user reports bugs). Creates Beads issues for all problems...
Clean code principles, error handling patterns, and coding standards for PACT Code phase. Use when: implementing features, refactoring code, reviewing code quality, establishing coding conventions, or handling...
Evaluate code review quality and provide feedback on review effectiveness and thoroughness
Local code review using CodeRabbit CLI. Use when user wants to review changes before committing or pushing.
Full project code review using multiple AI CLIs (Claude, Gemini, Codex). Use when user wants comprehensive multi-perspective code review.
Comprehensive code review checking quality, security, and best practices. Triggers: CR, review, 審查, 檢查, check, 看一下, PR, code review, 品質.
Use when receiving code review feedback, before implementing suggestions. Requires technical verification, not performative agreement or blind implementation.
This skill should be used when managing the file-based todo tracking system in the .ai/todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integr...
This skill should be used when the user asks to "review code", "review this PR", "code review", "audit this code", or mentions reviewing pull requests, security checks, or code quality. Covers security (OWASP),...
Sarcastic QA Lead who audits codebases for code smells, anti-patterns, and WTF moments. Provides best-practice fixes with cutting wit. Use for code reviews and quality audits.
Apply when reviewing pull requests, conducting code reviews, or self-reviewing code before submission.
Perform and apply code reviews (UACRP + application protocol) and coordinate artifacts via mpcr.
Review code changes in GitHub pull requests or local git branches against main branch. This skill should be used when users request code review for PRs or branch changes in git repositories.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable
Perform code review, analyze code quality, find bugs, suggest improvements, check best practices and coding standards.
Use when executing implementation plans with independent tasks in the current session or facing 3+ independent issues that can be investigated without shared state or dependencies - dispatches fresh subagent fo...
Routes tasks to appropriate Task tool agents (subagents). Triggers on complex multi-step tasks, research, code review, exploration, or any task benefiting from specialized agent execution. Matches intent to age...
Full-context code review with multi-pass synthesis
AI-powered code review using CodeRabbit CLI. Use when reviewing code changes, checking PR readiness, getting feedback on staged/committed changes, or when the user mentions code review, CodeRabbit, or wants the...
Reviews code for logic flaws, edge cases, performance bottlenecks, security vulnerabilities, maintainability concerns, architecture best practices, and adherence to local patterns and CLAUDE.md guidelines. Use...
Get git records for specified users and days, perform code review for each commit, and generate detailed code review reports
Write and generate code using memex-cli with Codex backend. Use when (1) Generating code files and scripts, (2) Refactoring existing code, (3) Writing tests, (4) Creating project scaffolds, (5) Implementing alg...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.