Review current git changes for design, security, and performance issues.
npx skills add https://github.com/cenjie/skills --skill code-review-expert-cenjie
Please help me install this Agent Skill. Skill: code-review-expert Source: https://github.com/cenjie/skills/tree/main/skills/code-review-expert Command: npx skills add https://github.com/cenjie/skills --skill code-review-expert-cenjie
This skill helps engineering teams and reviewers quickly and consistently evaluate current git changes to identify SOLID/design violations, security vulnerabilities, performance regressions, error-handling gaps, and unsafe removal candidates before merging.
Review the current git changes and produce a prioritized code review summary with P0-P3 findings.
High-intent search queries and answers about installing and using this skill.
Review git changes for SOLID violations and security vulnerabilities by running a structured preflight that scopes diffs to detect SRP, OCP, LSP, ISP, and DIP issues alongside XSS, injection, and SSRF flaws. The skill produces prioritized P0-P3 findings with refactor rationale.
Finding dead code and planning safe removal in a pull request involves identifying unused or dead code candidates and generating a safe-delete versus defer plan. The skill provides verification steps and rollback guidance while awaiting explicit user confirmation before making changes.
Yes, you can detect race conditions and N+1 queries in staged git changes. The skill performs security and reliability scanning to flag race conditions and assess exploitability, while performance checks identify N+1 queries, CPU hotspots, and missing caching.
A code review handles large diffs by using git status and diffs to scope changes, summarizing them by file or module. It groups related concerns by feature, producing reference-based checklists and incremental refactor plans mapped to severity levels.
Yes, the code review process checks error-handling gaps and boundary-condition bugs. It identifies swallowed exceptions and boundary issues during performance and code quality analysis, mapping all findings to severity levels from P0 to P3.
You should use an automated code review when evaluating git changes, staged code, or commit ranges for architecture defects, unsafe removal candidates, and performance regressions. It ensures consistent evaluation before merging while waiting for explicit user confirmation.
Sh3rd3nAutomate two-stage code review for spec compliance and code quality.
andregusman-raizAnalyze code patterns and tech debt to produce P0-P3 prioritized findings.
SHINZO111Analyze latest git changes for SOLID violations and security risks.
antoniocascaisAudit git diffs, commits, branches, and pull requests for security and dependency issues.
