code-reviewer
Perform systematic code reviews following best practices and team standards
Skills matching the name, description or GitHub author.
Perform systematic code reviews following best practices and team standards
Best practices for performing thorough, constructive code reviews. Use when reviewing PRs to ensure quality feedback that improves code and helps developers grow.
Use when receiving code review feedback - requires technical evaluation and verification, not performative agreement or blind implementation
Senior Frontend Code Reviewer with 12+ years JavaScript/TypeScript experience. Use when reviewing React/TypeScript code, checking code quality and style, verifying accessibility compliance, ensuring test covera...
Senior Backend Code Reviewer with 12+ years Java experience. Use when reviewing Java/Spring code, checking code quality and style, identifying code smells and anti-patterns, verifying security practices, ensuri...
Rev - Senior Full-Stack Code Reviewer with 12+ years experience in Java/Kotlin and TypeScript/React. Use when reviewing code quality, checking security vulnerabilities, validating style compliance, running stat...
Provides the complete code review scoring rubric with 10 weighted categories, severity multipliers, and deduction calculations. Use when performing quantified code reviews, calculating quality scores, or creati...
Comprehensive code review with multi-agent analysis. Checks security, performance, maintainability, tests.
Code review checklist for SwiftUI and Swift PRs. Use when reviewing pull requests, checking code quality, verifying Swift/SwiftUI implementations, or conducting PR reviews. Provides prioritized checklist coveri...
Code review workflow using GitHub CLI. Use when reviewing pull requests, checking PR diffs, adding review comments, or approving/requesting changes on PRs.
Use for code review - runs all reviewers in parallel on uncommitted changes
Perform a code review on recent changes
Comprehensive code review framework for evaluating implementations against plans, requirements, and quality standards. Provides structured analysis with prioritized, actionable feedback.
接收代码审查反馈时使用,在实施建议之前,特别是当反馈不清晰或技术上有疑问时。需要技术严谨和验证,而不是盲目实施。Use when receiving code review feedback - requires technical rigor and verification, not blind imp...
Autonomous code review for best practices, security, performance, and potential issues. Runs in isolation with read-only tools using Opus model. Use when reviewing code, checking PRs, or analysing code quality.
Confidence-based code review that filters issues to 80+ threshold, eliminating false positives and noise. Reviews implementation against plan or requirements for bugs, quality issues, and project conventions. U...
Perform thorough code reviews with focus on security, performance, maintainability, and best practices. Use when reviewing code changes, pull requests, entire files, or codebase audits across any programming la...
Comprehensive Rust development guidelines based on 6 months of code reviews. Use when writing Rust code, debugging Rust issues, or reviewing Rust PRs. Covers error handling, file I/O safety, type safety pattern...
Apply comprehensive code review checklist covering purpose, design, quality, correctness, security, performance, testing, and documentation. Use when reviewing pull requests, conducting code reviews, or self-re...
Code reviewer providing objective quality metrics, security analysis, and actionable feedback. Use for code reviews with scoring, linting, type checking, and duplication detection.
ADVISORY validation of code against design principles that linters cannot enforce. Loaded by go-code-reviewer agent for design analysis guidance. Also invoked by @refactoring (after pattern application). Can be...
This skill should be used as REQUIRED Phase 6 of /dev workflow when the implementation is complete and needs code review. Combines spec compliance and code quality checks with confidence-based filtering.
Verification-first approach to code review feedback. Use when receiving review comments during the implement phase. Evaluate suggestions rigorously before implementing - no performative agreement.
Code review methodology for evaluating implementation changes. Use when reviewing code changes for quality, design, correctness, and maintainability. Focuses on changes made during implementation using Conventi...
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.