ankyr-ci-local-review-loop

Runs an iterative local code review loop with user-approved fixes until zero findings remain.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/GuyErreich/AI_Agents --skill ankyr-ci-local-review-loop-guyerreich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ankyr-ci-local-review-loop
Source: https://github.com/GuyErreich/AI_Agents/tree/main/plugins/ankyr-review/skills/ankyr-ci-local-review-loop
Command: npx skills add https://github.com/GuyErreich/AI_Agents --skill ankyr-ci-local-review-loop-guyerreich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Local changes often accumulate review findings that are only caught after a pull request is opened, forcing costly rework cycles. This Skill drives the working tree to zero review findings before a milestone, keeping the user in control of every fix decision. ## Core Features & Use Cases - Controlled Review Loop: Repeatedly reviews local changes, presents a triage table, and re-reviews after fixes until findings reach zero or the user stops. - User-Gated Triage: Every finding is classified as fix now, by design, or defer, and only user-approved fixes are implemented with minimal root-cause changes. - No Auto Commit: The loop never commits or pushes automatically; it only offers to hand off to a commit skill when the user asks. - Use Case: Before cutting a release, run the loop on a feature branch to review the diff, approve targeted fixes, validate against the repo's AGENT.md Validate suite, and finish with a clean tree ready to commit. ## Quick Start Run the local review loop on my current changes and triage the findings with me before fixing anything.

Frequently Asked Questions about ankyr-ci-local-review-loop

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

FAQPage Schema
How do I review local code changes before committing?▼

Run the local review loop on your working tree diff. It reviews the changes, presents a triage table of findings, implements only the fixes you approve, validates, and re-reviews until no findings remain.

How to run a code review on a specific file or module?▼

Supply a path scope such as a file, module, or package when invoking the loop. The reviewer then runs at the file argument tier on that path instead of the default change-tier diff.

Does the local review loop commit changes automatically?▼

No, the loop never auto-commits or auto-pushes. When it ends clean, it only offers to hand off to the commit skill if you explicitly ask to commit.

Can I keep intentional design choices flagged as findings?▼

Yes, mark any finding as by design with a one-line rationale and it is kept. The loop ends when remaining findings are all accepted by design or fixed.

What standards does the reviewer apply to findings?▼

Standards resolve in order: the AGENT.md chain from leaf to root, then project rules, then project skills, then the plugin's matching skill. Every finding must trace to a standard that applies to the project.