skills.rest
johnend
johnendCOMMUNITY
Explore all skills by this author →
GitHub

review-local

Identify defects and risks in local code changes with severity-ordered findings.

23|3|Updated May 17, 2024
Search Tags:#git#review#diff#pre-commit#code-quality#findings#local-changes
One-click install
npx skills add https://github.com/johnend/dots --skill review-local-johnend
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-local
Source: https://github.com/johnend/dots/tree/main/common/.ai/skills/review-local
Command: npx skills add https://github.com/johnend/dots --skill review-local-johnend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review and surface bugs, regressions, risk, and missing tests in your local changes without altering code.

Core Features & Use Cases

  • Severity-first findings prioritization to help triage quickly.
  • Dual-scope support: working-tree (uncommitted and staged) and branch diff vs base (pre-PR self-review).
  • Concrete file references in findings to enable immediate remediation.
  • Read-only operation: does not edit code or commit changes.

Quick Start

Ask me to review your current local changes and I will generate a structured findings report.

Frequently Asked Questions about review-local

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

FAQPage Schema
How do I review local git changes for defects before committing?▼

To review local git changes for defects, you can analyze uncommitted and staged working-tree changes to identify bugs, regressions, and missing tests, producing a structured findings report without altering your code.

Can I generate a pre-PR self-review report from a branch diff?▼

Yes, you can generate a pre-PR self-review report by comparing a branch diff against its base, surfacing risks and missing tests with concrete file references to enable immediate remediation before merging.

How does a severity-first code review report help triage local changes?▼

A severity-first code review report prioritizes findings by impact, helping you triage local changes quickly by highlighting the most critical defects and risks before addressing lower-priority issues.

Does reviewing local code changes automatically edit my working tree?▼

No, reviewing local code changes is a read-only operation that does not edit code or commit changes, ensuring your working tree remains untouched while you analyze the generated findings report.

What is the best way to find bugs and regressions in staged git changes?▼

The best way to find bugs and regressions in staged git changes is to run a read-only review that targets the working-tree scope, producing a structured report with concrete file references for immediate remediation.

Related Skills

Explore More Software Engineering Skills→
windmill-labswindmill-labs
17.5k

pr

Create draft GitHub pull requests with conventional commit titles.

Official
Advanced
obada-jarasobada-jaras

code-review

Review Git repository code changes for security and correctness defects.

Community
Advanced
gkganesh12gkganesh12
1

gk-review

Audit source code against documentation and test suites for architectural drift.

Community
Advanced
julian-galluzzojulian-galluzzo
99

marko

Review git diffs and source files for concrete defects and risks.

Community
Intermediate