review-and-fix-git-status

Reviews uncommitted git changes, fixes bugs, and re-runs CI gates until green.

10|1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/catalystctl/catcode --skill review-and-fix-git-status-catalystctl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-and-fix-git-status
Source: https://github.com/catalystctl/catcode/tree/main/.catalyst-code/skills/review-and-fix-git-status
Command: npx skills add https://github.com/catalystctl/catcode --skill review-and-fix-git-status-catalystctl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Uncommitted feature work often hides logic bugs and formatting or lint drift that fail CI gates even when the code compiles. This Skill reviews the working-tree diff, fixes issues it finds, and loops verification until every CI gate passes. ## Core Features & Use Cases - CI Gate Verification: Runs the exact CI checks (cargo fmt --check, clippy, cargo test, go vet, tsc) against the real workflow config instead of trusting that the code merely builds. - Diff-Focused Bug Review: Reads each changed file's diff for control-flow errors, mirrored-logic drift, shared-state hazards, and off-by-one boundary bugs. - Concurrent Session Isolation: Distinguishes errors in files you touched from in-flight work by other agent sessions, avoiding accidental interference. - Use Case: After finishing a feature across the Rust core and Go TUI, ask for a review of your uncommitted changes; the Skill finds a formatting failure and a duplicated-list drift bug, fixes both, and re-runs all gates until green. ## Quick Start Review my uncommitted git changes, fix any bugs or issues you find, and keep looping until all CI checks pass.

Frequently Asked Questions about review-and-fix-git-status

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

FAQPage Schema
How do I review uncommitted git changes for bugs before committing?

Run git status and git diff --stat to scope the changes, then read each changed file's diff for control-flow errors, duplicated-logic drift, and boundary bugs. Verify with the exact CI gates such as cargo fmt --check, clippy, and the test suites rather than trusting that the code compiles.

Why does my code pass cargo check but still fail CI?

Compilation checks validate only that code builds, not formatting or lint gates. A green cargo check with a failing cargo fmt --check still fails CI, so run the exact commands from the CI workflow configuration.

How do I capture the real exit code of cargo fmt through a pipe?

Piping cargo fmt --check to tail makes $? report tail's exit code, masking fmt's failure. Redirect output to a temp file and echo $? afterward, or check PIPESTATUS[0] to get the real exit status.

Should I fix compile errors in files I did not touch?

No. Errors in files outside your diff are usually a concurrent agent session's in-flight work. Isolate verification to the files your git diff touches and leave the rest to the owning session.

When should I use this instead of a full production-readiness review?

Use this when the scope is the current uncommitted diff for a feature, not the whole repository. A full-repo audit belongs to a production-readiness review; this workflow targets working-tree changes only.