Review code changes for security, performance, and correctness issues.
npx skills add https://github.com/ngochuy13/intern-dev --skill code-review-ngochuy13
Please help me install this Agent Skill. Skill: code-review Source: https://github.com/ngochuy13/intern-dev/tree/main/skills/code-review Command: npx skills add https://github.com/ngochuy13/intern-dev --skill code-review-ngochuy13
Code changes can introduce security vulnerabilities, performance regressions, or subtle correctness bugs that are hard to spot during busy development cycles.
Use the command /code-review <PR URL or file path> and share the diff (or the files) you want reviewed before merging.
High-intent search queries and answers about installing and using this skill.
To review PR diffs for security vulnerabilities and performance regressions, analyze the code changes to identify injection risks, authentication flaws, N+1 query problems, and error handling gaps, then generate actionable findings organized by severity and category.
A code security audit and performance check covers OWASP-style injection risks, secrets leakage, authentication flaws, unbounded loops, inefficient algorithms, resource leaks, and N+1 query problems to prevent security vulnerabilities and performance regressions.
Checking code changes for correctness defects and maintainability issues involves examining edge cases, race conditions, error handling gaps, and code clarity, producing structured assessments with actionable guidance to prevent subtle bugs from shipping.
Yes, automated code review can be applied to targeted file paths as well as full PR diffs, providing a structured assessment of injection risks, N+1 queries, and edge cases wherever a detailed security and performance evaluation is needed.
The best way to prevent N+1 queries and secrets leakage before merging code is to run a structured review on the diff that flags performance regressions and security vulnerabilities, organizing findings by severity across Security, Performance, Correctness, and Maintainability dimensions.
Yes, automated code review works on unmerged pull request diffs by reviewing the proposed code changes to catch injection risks, correctness defects, and performance regressions before they ship, ensuring the final merge maintains security and quality standards.
alo-expAnalyze code changes for security, performance, and correctness across pull requests or diffs.
peancharoenReview git diffs and file paths for code issues with severity labels.
UnicornReview code changes for defects, style violations, and maintainability issues.
mgd34msuAudit code for security vulnerabilities, performance issues, and complexity metrics.
