skills.rest
aitit-inc
aitit-incOFFICIAL
Explore all skills by this author →
Website𝕏@SurpassOne_001GitHub

quick-review

Reviews code changes for bugs and reports findings with file and line references.

3|Updated May 28, 2026
Search Tags:#code review#pull request#subagent#bug detection#git diff#pre-merge
One-click install
npx skills add https://github.com/aitit-inc/leadace --skill quick-review-aitit-inc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quick-review
Source: https://github.com/aitit-inc/leadace/tree/main/.claude/skills/quick-review
Command: npx skills add https://github.com/aitit-inc/leadace --skill quick-review-aitit-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When your primary code review tool (Codex) is unavailable or out of credits, you still need a fast, bug-focused review of uncommitted diffs, branch changes, or open pull requests without modifying any files. ## Core Features & Use Cases - Bug-Focused Review: Analyzes uncommitted diffs, branch diffs, or open PRs with a strict focus on defects rather than style. - Read-Only Reporting: Reports findings with precise file:line references and never edits source files. - Forked Subagent Execution: Runs as a forked Fable subagent at high effort for deeper reasoning on the change. - Use Case: You are about to merge a feature branch but Codex is out of credits, so you trigger a quick review to catch logic errors and regressions before merging. ## Quick Start Ask Claude to run a quick review of the current branch diff and report any bugs with file and line numbers.

Frequently Asked Questions about quick-review

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

FAQPage Schema
How do I review a code change for bugs without Codex?▼

Trigger the quick-review skill by saying 'quick review' in your Claude session. It analyzes the uncommitted diff, branch diff, or open PR and reports bugs with file:line references without editing any files.

What triggers the quick-review skill?▼

The skill activates on the phrases 'quick review', 'quick-review', or the Japanese 'クイックレビュー'. It is designed as a fallback when Codex is unavailable or out of credits.

Does quick review modify my code during analysis?▼

No, the skill is strictly read-only. It reviews the change and reports findings with file:line locations, leaving all source files untouched.

What kinds of changes can quick review analyze?▼

It handles uncommitted diffs, branch diffs, and open pull requests, choosing whichever fits the current context. The review focuses specifically on bugs rather than style or formatting.

When should I not use quick review?▼

Avoid it when you need style, architecture, or documentation feedback, since it focuses only on bugs. For comprehensive reviews, use your primary review tool such as Codex when it is available.

Related Skills

Explore More Software Engineering Skills→
AradotsoAradotso
4

stage-cli-code-review

Organize local git diffs into logical chapters for code review.

Official
Intermediate
prthikprthik
1

code-review

Review code changes for quality, security, and maintainability issues.

Community
Advanced
zajcazajca
2

go-linting

Configure golangci-lint with recommended Go linters for static analysis.

Community
Basic
verivus-ossverivus-oss
10

multi-llm-review

Review code concurrently with multiple AI models and MCP tools.

Official
Advanced