skills.rest
nijaru
nijaruCOMMUNITY
Explore all skills by this author →
Website𝕏@nijaru0xGitHub

review

Identify defects in source code during reviews.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nijaru/dotfiles --skill review-nijaru
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/nijaru/dotfiles/tree/main/private_dot_codex/skills/review
Command: npx skills add https://github.com/nijaru/dotfiles --skill review-nijaru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill performs a thorough review of code quality, security, and performance, helping you catch issues before they reach production.

Core Features & Use Cases

  • Scope Detection: Review specific files, diffs on a feature branch, or staged/unstaged changes.
  • Checklist: Design, naming, comments, correctness, security, and performance.
  • Output: A concise report listing issues by severity with suggested fixes.

Quick Start

Review your current changes and get a structured report you can act on.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review code for security and quality issues before merging?▼

Code review identifies defects across design, naming, comments, correctness, performance, and security. Run the review on your feature branch, staged changes, or diffs against main to catch issues before production and get a severity-ranked report with suggested fixes.

Can I review specific files or just diffs in my branch?▼

Yes, the review supports multiple scopes: specific files, diffs on a feature branch against upstream, staged changes, and unstaged changes. Choose the scope that matches your workflow—pre-commit, pre-merge, or post-implementation assessment.

What does a code review checklist typically cover?▼

A thorough code review examines design integrity, naming conventions, comment clarity, correctness of logic, performance implications, and security vulnerabilities. The output lists each issue by severity with actionable fix suggestions.

When should I run a code review in my development workflow?▼

Run code review during feature-branch reviews before merging, as a pre-merge quality gate, or after implementation to assess overall code quality. It works at any stage where you need structured defect detection.

How detailed is the review output?▼

The review produces a concise, severity-ranked report listing detected issues with suggested fixes. Output is structured for quick triage so you can prioritize what to address before commit or merge.

Related Skills

TokenRollAITokenRollAI
459

commit

Generate commit messages from git diffs and project history.

Official
Intermediate
dnvitidnviti
10

vulnerability-create

Generate structured remediation tasks from security vulnerability findings with severity classification.

Community
Intermediate
0xtaoist0xtaoist

ln-741-linter-configurator

Generate linting, formatting, and static analysis configs for TypeScript, Python, and .NET.

Community
Advanced
jangtrinhjangtrinh

code-review-checklist

Identify code defects and security vulnerabilities using a structured review checklist.

Community
Intermediate