Skills matching the name, description or GitHub author.
Setup and troubleshoot GitHub Actions workflows using anthropics/claude-code-action for automated PR reviews. Use when creating CI/CD workflows that leverage Claude for code review, research validation, or auto...
Systematic code review for TapScore focusing on code smells, duplication, architecture violations, and security issues. Use when reviewing code changes before commit or merge. Provides constructive feedback wit...
Automated TFVC code review for Azure DevOps changesets with Snyk security scanning and Notion integration
Phased Implementation Supervisor to coordinate coding and code review subagents. Use this skill when the user has an implentation plan file and wants to execute it phase by phase with build verification, testin...
Critical code review methodology. Use when reviewing code, PRs, or changes to enforce rigorous review standards.
Python code review specialist. Use when reviewing Python code, checking for bugs, security issues, or ensuring code quality standards.
PROACTIVELY USED when reviewing a PR, branch, or Jira story. Handles code review against requirements and provides actionable feedback.
Systematically fetch, analyze, and fix code review issues from GitHub Pull Requests. Use when the user asks to review and fix code issues from AI code reviewers (like Gemini Code Assist, GitHub Copilot, CodeRab...
Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success c...
Copilot agent that assists with comprehensive code review focusing on code quality, SOLID principles, security, performance, and best practices Trigger terms: code review, review code, code quality, best pract...
Development workflow for code changes. Load when: implementing features, fixing bugs, writing tests, refactoring, creating PRs, reviewing code. Covers exploration → design → implementation → commit → PR cycle....
Expert code reviewer for Python, TypeScript, and general best practices
Automated code review for quality, security, and best practices. Use when user asks for code review, quality analysis, or wants feedback on their code.
Build a complete data clustering and visualization pipeline from any data source. Use when the user wants to analyze patterns in text data (GitHub issues, Slack messages, support tickets, code reviews, forum po...
Perform code review with DDD architecture compliance check. Triggers: review, 程式碼審查, code review, 審查, CR.
Code review. Use for 'code review', 'PR review', 'review this' requests
Translate SQL queries into plain language business logic. Use when documenting queries, explaining analysis to non-technical stakeholders, code review, or creating user-friendly query descriptions.
Systematic code review checklist for quality, correctness, and maintainability
Automated AI-powered code review that runs on git hooks with progressive disclosure design. Use when setting up automated code review for a project, installing git hooks for code review, creating or modifying r...
Use immediately when user mentions: "code review", "コードレビュー", "レビュー", "review", "品質", "quality", "チェック", "check", "lint", "format", "test", "type check", "pyright", "ruff", "pytest", "テスト",...
Comprehensive code review for quality, architecture, and performance. Use when reviewing PRs, auditing code quality, checking coding standards, evaluating design patterns, identifying performance bottlenecks, o...
Systematically fetch, analyze, and fix code review issues from GitHub Pull Requests. Use when the user asks to review and fix code issues from AI code reviewers (like Gemini Code Assist, GitHub Copilot, CodeRab...
Idiomatic Go patterns and conventions from official Effective Go guide. Use when writing Go code to ensure proper naming, error handling, concurrency patterns, interface design, and Go-specific idioms. Triggers...
code review
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.