code-reviewer
Elite code review agent for comprehensive analysis of code quality, security, performance, and architecture. Use when reviewing PRs, analyzing code changes, checking for bugs, security vulnerabilities, or perfo...
按技能名称、说明或 GitHub 作者匹配的结果。
Elite code review agent for comprehensive analysis of code quality, security, performance, and architecture. Use when reviewing PRs, analyzing code changes, checking for bugs, security vulnerabilities, or perfo...
Use when the user needs technical research, architecture validation, documentation generation, or code review. Default is read-only mode, but can enable auto-approve (-y) for code changes.
Automatically triggered for code reviews, PR analysis, and quality checks. Use when reviewing changes, checking code quality, or preparing commits.
Code quality - patterns, testing, maintainability. Use for code review.
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...
General code review for staged changes or specified files. Use when reviewing pull requests, commits, or code changes across any language.
GitHub PR utilities for code review workflows
systematic code review for correctness, security, style, and performance. Use this when the user asks for a review or before committing significant changes.
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
接收代码审查反馈时使用,在实施建议之前,特别是当反馈不清晰或技术上有疑问时。需要技术严谨和验证,而不是盲目实施。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...
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。