Agent skill

Quick Review

by meain in meain/dotfiles

Lightweight code review via subagent. An agent skill from meain/dotfiles.

MITAuto-check passedAgent Workflows

Install Quick Review

skills CLI
$ npx skills add meain/dotfiles --skill quick-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install meain/dotfiles quick-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/meain/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/agents/.agents/skills/quick-review .claude/skills/quick-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
quick-review
GitHub stars
285
Token cost
~710 tokens
SKILL.md length
285 words
Files
1
Skills in repo
35
Repo updated
First seen
Licence
MIT

At a glance

Lightweight code review via subagent. An agent skill from meain/dotfiles.

  • Works in 4 steps: Identify commits to review → Build context → Spawn the review subagent (background) → …
  • The user says /quick-review
  • SKILL.md covers Step 1: Identify commits to…, Step 2: Build context, Step 3: Spawn the review… and Step 4: Report
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Quick Review is an agent skill from meain/dotfiles. Lightweight code review via subagent. The main agent identifies commits and passes them to a subagent that retrieves the changes and reviews for correctness issues, consistency problems, and gaps. No praise, no style nits. Use when the user says /quick-review, "review my changes", "review this diff", "sanity check my code", or after finishing a feature/fix and wanting a second opinion before pushing.

Its SKILL.md is about 710 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Subagents. The repository describes itself as: If there is a shell, there is a way! The licence is MIT.

When your agent uses it

  • The user says /quick-review
  • Review my changes
  • Review this diff
  • Sanity check my code

Example prompts

  • “review my changes”
  • “review this diff”
  • “sanity check my code”
  • “/quick-review”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Identify commits to review
  2. Build context
  3. Spawn the review subagent (background)
  4. Report

What it can do on your machine

Read from SKILL.md and the folder at commit 3e336e2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Quick Review loads about 710 tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 285 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~104
When it runs · the whole SKILL.md, loaded when a task matches
~710

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from meain/dotfiles at commit 3e336e2, republished under its MIT licence (© meain). 285 words, ~710 tokens.

Download SKILL.mdSave it as .claude/skills/quick-review/SKILL.md (or your agent's skills folder).
name
quick-review
description
Lightweight code review via subagent. The main agent identifies commits and passes them to a subagent that retrieves the changes and reviews for correctness issues, consistency problems, and gaps. No praise, no style nits. Use when the user says /quick-review, "review my changes", "review this diff", "sanity check my code", or after finishing a feature/fix and wanting a second opinion before pushing.

Spin up a subagent to review the relevant commits. Run in background so the main thread isn't blocked.

Step 1: Identify commits to review

The main agent (you) knows which commits are relevant — use that context. Do NOT assume the working copy is empty or that everything above trunk() is in scope. Common cases:

  • User just made one or more commits → pass those specific commit IDs
  • User is working on a branch → pass the commits that make up the feature
  • User provides a description → infer from context which commits apply

If unclear, ask which commits to review before spawning the subagent.

Step 2: Build context

Build a brief with:

  • What: what the change does (from commit messages or user args)
  • Why: why the change was made — the problem being solved, the incident that prompted it, the constraint being addressed. Pull this from the conversation context; don't just restate the what.
  • Background: any domain context the reviewer needs to assess correctness — e.g. how the system works, what the replaced code did, relevant constraints.

The richer this brief, the more useful the review. A reviewer who understands why a change was made can spot gaps the diff alone won't reveal.

Step 3: Spawn the review subagent (background)

Pass the commit IDs and context. The subagent will retrieve the changes itself and may read any files or run any checks it needs.

Prompt template:

Review the following commits in <repo-path>:
<commit IDs, one per line>

What: <what the change does>
Why: <why the change was made — problem, incident, constraint>
Background: <any domain context needed to assess correctness>

Retrieve the changes, then review for: correctness bugs, broken invariants,
consistency issues with surrounding code, clear gaps or missing cases. You may
read any files in the repo or run any checks needed to assess correctness.

Return only actionable findings — one bullet per finding.
No praise. No style nits. No commentary on what the code does.
If nothing to flag, say "Nothing to flag."

Set run_in_background: true.

Step 4: Report

Wait for the background subagent to complete, then return its findings verbatim.

Stop here. Do NOT attempt to fix any of the findings. The user reads the findings and decides what to act on. Only make changes if the user explicitly asks for them after seeing the report.

© meain, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in agents/.agents/skills/quick-review of meain/dotfiles.

Open the folder on GitHubat commit 3e336e2

Compare with similar skills

Quick Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Quick Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Quick Review this skillmeain/dotfiles285—~710Automated safety check: PassMIT
O2 Review Loopopenobserve/openobserve22k—~3.7kAutomated safety check: PassAGPL-3.0
V2 Perf Iterationmirage-project/mirage2.5k—~4kAutomated safety check: PassApache-2.0
Clone App Pat Proper-simmons/clone-app-pat-pro-public259—~1.9kAutomated safety check: NotesNone
Kimi Code DelegationCherryHQ/cherry-studio52k—~504Automated safety check: PassAGPL-3.0
Swarm Orchestrationruvnet/ruflo74k2 repos~779Automated safety check: PassMIT

Similar skills

  • O2 Review Loop

    openobserve/openobserve

    Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.

    22k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • V2 Perf Iteration

    mirage-project/mirage

    Runtime-V2 performance-iteration workflow. An agent skill from mirage-project/mirage.

    2.5k GitHub stars~4k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed
  • Clone App Pat Pro

    per-simmons/clone-app-pat-pro-public

    Clones any web app pixel-for-pixel from a URL. An agent skill from per-simmons/clone-app-pat-pro-public.

    259 GitHub stars~1.9k tokensUpdated 4 mo ago
    Agent WorkflowsAuto-check: notes
  • Kimi Code Delegation

    CherryHQ/cherry-studio

    Delegates one bounded repository task to Kimi Code in non-interactive prompt mode and reads back the final result from its JSON event stream.

    52k GitHub stars~504 tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Coordinates a hierarchical swarm of specialized agents through the claude-flow CLI for work that spans several files or modules at once.

    74k GitHub starsUsed in 2 repos~779 tokens
    Agent WorkflowsAuto-check passed
  • Team Mode

    oil-oil/codex-team-mode

    A skill your agent uses when a task may benefit from a bounded subagent for implementation, large-codebase discovery at task start, independent review, requested or pre-commit code simplification…

    217 GitHub stars~1.3k tokensUpdated 8 days ago
    Agent WorkflowsAuto-check passed

More from meain/dotfiles

All 35 skills in this repo
  • Recall

    meain/dotfiles

    Search past Claude Code and Codex sessions. An agent skill from meain/dotfiles.

    285 GitHub starsUsed in 1 repo~684 tokens
    Auto-check passed
  • Grill With Docs

    meain/dotfiles

    Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.

    285 GitHub starsUsed in 20 repos~875 tokens
    Auto-check passed
  • Backlog

    meain/dotfiles

    Daily backlog management — full planning review OR add a single entry from a URL.

    285 GitHub stars~3k tokensUpdated yesterday
    Auto-check passed
  • Concern Review

    meain/dotfiles

    Generate an interactive local HTML review page for a large PR or diff, grouping the changed files by logical concern (not just by file) so a reviewer can go through one theme at a time instead of a…

    285 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed
  • My Weekly Report

    meain/dotfiles

    Generate a concise weekly status update in team format. An agent skill from meain/dotfiles.

    285 GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed
  • Web Search

    meain/dotfiles

    Search the web using lynx and DuckDuckGo. An agent skill from meain/dotfiles.

    285 GitHub stars~830 tokensUpdated yesterday
    Auto-check passed

Questions about Quick Review

What does Quick Review do?

Lightweight code review via subagent. An agent skill from meain/dotfiles. Quick Review is an agent skill from meain/dotfiles. Lightweight code review via subagent.

When should I use Quick Review?

Quick Review fits situations like: the user says /quick-review; review my changes; review this diff; sanity check my code.

How do I install Quick Review in Claude Code?

Run `npx skills add meain/dotfiles --skill quick-review -a claude-code`. Or copy the skill folder (agents/.agents/skills/quick-review in meain/dotfiles) into .claude/skills/quick-review in your project. Claude Code loads it when a task matches its description.

How do I install Quick Review in Codex?

Run `npx skills add meain/dotfiles --skill quick-review -a codex`. Or copy the skill folder (agents/.agents/skills/quick-review in meain/dotfiles) into .agents/skills/quick-review in your project. Codex loads it when a task matches its description.

Can I use Quick Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add meain/dotfiles --skill quick-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/quick-review, .gemini/skills/quick-review, .github/skills/quick-review and .opencode/skills/quick-review in your project.

What does Quick Review need to run?

SKILL.md names no scripts, command-line tools or credentials: Quick Review is instructions for the agent only.

Does Quick Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Quick Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Quick Review use?

Quick Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Quick Review use?

About 710 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Quick Review?

Skills that share tags, products or a category with Quick Review: O2 Review Loop (openobserve/openobserve, 22k stars), V2 Perf Iteration (mirage-project/mirage, 2.5k stars), Clone App Pat Pro (per-simmons/clone-app-pat-pro-public, 259 stars) and Kimi Code Delegation (CherryHQ/cherry-studio, 52k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Quick Review?

meain (a GitHub user) maintains it in meain/dotfiles, which has 285 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 8, 2026.

Source: meain/dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.