Review code changes for security, performance, and correctness issues.
npx skills add https://github.com/sun2443/designer-skills --skill code-review-sun2443
Please help me install this Agent Skill. Skill: code-review Source: https://github.com/sun2443/designer-skills/tree/main/engineering/skills/code-review Command: npx skills add https://github.com/sun2443/designer-skills --skill code-review-sun2443
It helps you catch defects and risks in pull requests before they reach production, reducing security exposure, performance regressions, and correctness bugs.
Run the skill with the command: /code-review <PR URL or file path>.
High-intent search queries and answers about installing and using this skill.
To review a pull request for security vulnerabilities and performance issues, analyze the code diff to identify injection risks, authz flaws, N+1 queries, and resource leaks before merging. This process produces a structured review with critical issues, file-line suggestions, and an approve or request-changes verdict.
Automated code review for pre-merge gating is the process of evaluating patch outputs and file-path change sets to catch correctness defects, maintainability issues, and security exposure before code reaches production. It generates a structured summary with actionable suggestions and a clear merge verdict.
To check code changes for edge cases and error handling defects, perform a correctness and maintainability review on the pull request diff. This identifies missing edge case coverage, race conditions, and readability problems, yielding a structured report with specific file and line suggestions.
Yes, you can use diff analysis to find maintainability and correctness bugs in patch outputs. By evaluating the code changes, you can detect insecure patterns, unbounded loops, and error handling gaps, resulting in a structured review summary with a clear verdict to approve or request changes.
Code review works with both specific file paths and full pull request URLs. You can run the analysis on file-path change sets or patch outputs directly, generating a structured summary with critical issues, file and line suggestions, and a final approve or request-changes verdict.
The best way to audit code for injection risks and missing authorization is to perform a security review on the pull request diff. This flags common vulnerabilities and secrets exposure, producing a structured review with critical issues, targeted file-line suggestions, and a clear verdict.
zyj18860969891-byteGenerate shareable diffs and patch views with viewer URLs and file artifacts.
QwenLMReview code changes for correctness, security, quality, and performance.
devsforgeRun TypeScript typecheck, ESLint, Prettier, tests, build, and npm audit gates.
brenordvAudit software systems for security vulnerabilities and regulatory compliance.
