skills.rest
nille
nilleCOMMUNITY
Explore all skills by this author →
𝕏@nilrodGitHub

Code Review

Review code diffs for correctness, security, and conventions.

Updated Apr 13, 2026
Search Tags:#security#review#diff#pr#code#naming#tests
One-click install
npx skills add https://github.com/nille/shipkit --skill code-review-nille
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Code Review
Source: https://github.com/nille/shipkit/tree/main/shipkit/core/skills/review
Command: npx skills add https://github.com/nille/shipkit --skill code-review-nille

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams perform structured reviews of code changes across local diffs, commits, and pull requests to catch bugs, security issues, and maintainability problems.

Core Features & Use Cases

  • Structured review focusing on correctness, security, error handling, naming clarity, duplication, and conventions.
  • Works across local changes, staged changes, commits, PRs, and branch diffs; reads surrounding context and checks for tests and project conventions.
  • Use Case: when a teammate submits a patch or PR, run this skill to generate an actionable, line-referenced review.

Quick Start

Provide a concise, actionable review of the specified diff or pull request.

Frequently Asked Questions about Code Review

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

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

Systematically review a pull request by analyzing the diff to evaluate correctness, security, error handling, and naming clarity. This process reads surrounding code context to ensure test coverage and conventions are respected, providing actionable line-referenced findings.

Can I run a code review on local staged changes before creating a commit?▼

Yes, you can run a code review on local staged changes before committing. The review applies to local diffs, staged changes, and branch diffs, identifying duplication and performance issues while checking project conventions to ensure code maintainability.

What is the best way to check if a code diff follows project naming conventions and has test coverage?▼

The best way to check naming conventions and test coverage in a code diff is to apply a structured review that reads surrounding context. This evaluates naming clarity and ensures tests exist for the modified code, yielding actionable findings with line references.

Does code review work with specific commit diffs or only full pull requests?▼

Code review works with both specific commit diffs and full pull requests. It analyzes code changes across local diffs, specific commits, PRs, and branch diffs, evaluating error handling and performance while respecting project conventions.

How do I get actionable line references when reviewing a branch diff for security vulnerabilities?▼

To get actionable line references when reviewing a branch diff for security vulnerabilities, apply a structured review to the diff. This evaluates security, correctness, and duplication, providing specific line references to pinpoint exact issues in the code changes.

Related Skills

Explore More Software Engineering Skills→
alexismanuelalexismanuel

git-commit-helper

Generate Conventional Commits messages from Git staged diffs.

Community
Intermediate
rysweetrysweet
1

simplify

Review changed code via git diffs and apply fixes for reuse, quality, and efficiency.

Community
Advanced
Marshall-HallenbeckMarshall-Hallenbeck
5

write-tests

Generate unit tests for Python, JavaScript, TypeScript, Rust, and Go modules.

Community
Advanced
eliottbusinesseliottbusiness

requesting-code-review

Automate pre-commit code review with static analysis and security scanning.

Community
Advanced