code-reviewer

Review local git diffs and generate a prioritized action plan.

3|Updated Mar 7, 2020
One-click install
npx skills add https://github.com/qsdrqs/dotfiles --skill code-reviewer-qsdrqs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/qsdrqs/dotfiles/tree/main/opencode/skills/code-reviewer
Command: npx skills add https://github.com/qsdrqs/dotfiles --skill code-reviewer-qsdrqs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Review local git diffs by producing a collaborative review plan and prioritized findings. This enables teams to quickly understand changes, plan investigations, and keep reviews lean and focused.

Core Features & Use Cases

  • Establish the diff scope fast: identify changed features, files, and likely entry points.
  • Produce a collaborative review plan: determine review order, modules/functions, and logic chain.
  • Surface prioritized findings: clearly label blockers and actionable improvements with evidence.

Quick Start

Run the code-reviewer on your current diff to generate a plan and prioritized notes.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I review a large local git diff before creating a pull request?

To review local git diffs, generate a collaborative review plan that establishes diff scope, determines review order, and surfaces prioritized findings with evidence-backed file:line references.

What is the best way to structure a code review for a complex refactor?

The best way to structure a code review is by producing a plan-focused summary that maps logic chains and modules, keeping investigations lean and focused even on large refactors.

Can I use this to review both staged and unstaged git changes?

Yes, you can review both staged and unstaged git changes. The process supports identifying changed files and entry points across both states to guide your walkthrough.

Does code review planning work without connecting to a remote repository?

Code review planning works on local git diffs directly, analyzing changes on your machine to produce prioritized notes without needing a remote repository connection.

How do I ensure code review findings are actionable and backed by evidence?

Ensure code review findings are actionable by enforcing evidence-backed reasoning with file:line references, clearly labeling blockers and improvements in the final summary.

When should I not use an automated diff walkthrough for code reviews?

Avoid automated diff walkthroughs when you need deep architectural validation rather than local change prioritization, as this focuses on lean, plan-based summaries for immediate diffs.