skills.rest
kiurakku
kiurakkuCOMMUNITY
Explore all skills by this author →
𝕏@thefear078GitHub

code-review

Reviews code diffs and PRs for security, correctness, performance, and maintainability issues.

15|3|Updated Jul 9, 2026
Search Tags:#code review#performance#pull request#security audit#merge#git diff#severity
One-click install
npx skills add https://github.com/kiurakku/cursor-kit-for-ai --skill code-review-kiurakku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/kiurakku/cursor-kit-for-ai/tree/main/plugins/engineering/skills/code-review
Command: npx skills add https://github.com/kiurakku/cursor-kit-for-ai --skill code-review-kiurakku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manual code reviews often miss critical issues like SQL injection, race conditions, or N+1 queries while wasting time on style nits that linters already catch. This Skill provides a structured, severity-ranked review process that focuses on what actually breaks production. ## Core Features & Use Cases - Four-dimension review: Audits security (injection, auth, secrets), correctness (edge cases, concurrency), performance (N+1 queries, missing indexes), and maintainability (dead code, test coverage). - Severity-ranked output: Classifies findings as Blocker, Major, Minor, or Nit with concrete failure scenarios and suggested fixes, producing a clear approve/request-changes verdict. - Use Case: Before merging a pull request, ask for a review of the branch diff. The Skill inspects each change in context, flags a missing webhook signature check as a Blocker with a fix snippet, and approves the rest. ## Quick Start Review the staged changes in this repository and report any security or performance issues with severity rankings.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a pull request for security issues?▼

Review the PR diff against four dimensions: injection, authentication/authorization, leaked secrets, and input trust boundaries. Verify each suspected issue by re-reading the surrounding code, then report only findings with a concrete failure scenario.

How to review code changes before merging a branch?▼

Run git diff main...HEAD to get the branch changes, then examine each hunk within its full function and caller context. Classify findings as Blocker, Major, Minor, or Nit, and include a fix snippet for every Blocker and Major issue.

What should a code review check besides style?▼

Focus on security flaws like SQL injection and missing auth checks, correctness issues like race conditions and swallowed exceptions, and performance problems like N+1 queries and missing indexes. Leave formatting to the project's linter.

Can this review staged changes instead of a full PR?▼

Yes, it supports staged changes via git diff --cached, branch diffs, specific files, or pending changes found through git status. If the working tree is clean, it asks what scope to review.

When should a code review not request changes?▼

Do not request changes for pure style when a formatter is configured, for issues in code the diff does not touch, or for speculative problems without a concrete failure mechanism. An empty Blockers section is a valid result.

Related Skills

Explore More Software Engineering Skills→
nillenille

Code Review

Review code diffs for correctness, security, and conventions.

Community
Advanced
tbeacktbeack
7

sec-review-fixes

Orchestrate security review findings into diffs, regression tests, and PRs.

Community
Advanced
Devsoul2026Devsoul2026
150

requesting-code-review

Automate pre-commit verification with static analysis, tests, and lint checks.

Community
Advanced
BluMintIncBluMintInc
2

automated-review-addressing

Automate pull request review feedback by updating the PR head branch.

Official
Advanced