Skills matching the name, description or GitHub author.
Validates TypeScript/React code against dev_instruction_v3.md standards. Checks for anti-patterns like export default, onClick usage, wrapper components, and any types. Use before committing or during code revi...
Comprehensive development workflow specialist combining TDD, debugging, performance optimization, code review, PR review, and quality assurance into unified development workflows
Implements a feature from a plan file in an isolated git worktree with e2e tests, parallel code review, and human review documentation. Use when implementing a planned feature with full validation and isolation...
Comprehensive code review with best practices, security, and maintainability checks. Use when reviewing pull requests, pre-commit code checks, learning code review techniques, improving code quality, or perform...
Create a template file for human reviewers to write free-form feedback before AI code review.
Conduct thorough, actionable code reviews that catch real problems without drowning in noise
Conduct structured implementation postmortems to gather feedback on architecture conformance, library friction, and tooling effectiveness. Use when reviewing completed implementations, PRs, or development phase...
Spawn parallel Claude Code sessions on git worktrees to review multiple projects simultaneously. Use when you have a monorepo or multi-project repo and want to run automated code reviews in parallel without man...
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement...
Opinionated constraints for writing maintainable, testable code. Apply MTE principles, avoid over-engineering, guide refactoring, and provide code review checklists. Use when users write code, refactor, or need...
GitHub development workflow best practices. Use when creating commits, pull requests, branches, reviewing code, managing issues, or any git/GitHub operations. Provides standards for commit messages, PR descript...
全面代码审查，检查安全漏洞、代码质量和最佳实践。 使用场景： - "code review" / "代码审查" / "审查代码" / "review 一下" - "检查代码质量" / "代码有什么问题" - "安全审查" / "找漏洞"
Code Reviewer persona for technical code analysis. ACTIVATE when messages contain review code, analyze code, code quality, best practices, refactor, improve code, check code, code review, look at code, feedback...
Perform code reviews for this No Name Running Club application (Next.js 16 App Router + React 19 + TypeScript + Tailwind CSS 4 + Prisma + NextAuth v5). Use when reviewing PRs/diffs, proposing architectural chan...
Generate a comprehensive code review prompt for the current branch that can be copied into another Claude session
Code review workflow with TODO tracking. Use when user says "review", "review-workflow", or asks to review code, PRs, or changes.
Comprehensive multi-AI consensus workflow for: 1. CODE REVIEW - Clinical/technical review following SOP with TODO.md/IDEAS.md tracking 2. ANALYSIS PLANNING - Statistical/bioinformatic analysis plans saved to an...
Performs comprehensive PR code review from 5 perspectives (quality/performance/tests/docs/security) in parallel, providing Blockers/Suggestions/Nice-to-have and merge decision. Args: /review [owner/repo] [pr-nu...
Orchestrates complex or architectural code changes through a structured workflow. Use when the user requests multi-file changes, new features, architectural refactoring, database schema changes, new API endpoin...
Perform a comprehensive code review of current uncommitted changes in a git repository. Analyzes for bugs, security vulnerabilities, best practices, DRY violations, code smells, performance issues, and areas of...
Code review for Next.js and TypeScript projects. Use when asked to "review this code", "check this PR", "review my changes", "look at this component", or any code review request. Applies team standards for Type...
Code review checklist covering security, performance, defensive programming, and testing anti-patterns. Use before merging PRs, after implementing features, or when reviewing code quality.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement...
Comprehensive code review of current branch using multi-agent verification across DDD/OOP compliance, DRY violations, clean code principles, architecture patterns, and test coverage
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.