ankyr-improve-code

Reviews and improves a named file, module, or package through a routed reviewer and fix loop.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you want to improve an existing file, module, or package rather than review a git diff, this Skill resolves the named path, applies the right language-specific review standards, and drives a structured findings-and-fix loop without expanding scope to unrelated changes. ## Core Features & Use Cases - Path-Scoped Review: Resolves the exact file, module, or package you name and reads the AGENT.md chain from that path up to the repo root so project standards always win. - Language Routing: Routes review through the reviewer skill's capability table, mapping .py and .pyi files to the python skill (and testing skill for test paths). - Findings-to-Fix Loop: Produces a findings table at the file-argument tier, then hands it to the ci-local-review-loop for triage, approved fixes, validation, and re-review. - Use Case: Ask to clean up a legacy Python module; the Skill reviews only that module, lists concrete issues, and iterates fixes until the loop ends clean, never auto-committing. ## Quick Start Ask the agent to improve or find issues in a specific path, for example: review and clean up the module at src/services/billing.py.

Frequently Asked Questions about ankyr-improve-code

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

FAQPage Schema
How do I improve a specific file or module instead of reviewing a git diff?▼

Name the file, module, or package and ask to improve it or find issues. The Skill resolves that path, reviews it at the file-argument tier, and drives a fix loop, keeping scope limited to what you named.

How does code review routing work for Python files?▼

Files ending in .py or .pyi are routed to the python skill through the reviewer skill's capability routing table. When the path is a test file, the testing skill is also loaded for the review.

Does improving code with this workflow auto-commit the fixes?▼

No, it never auto-commits. When the review loop ends clean with zero findings or accepted-by-design items, a commit is only offered if you explicitly ask for it.

What standards does the code review apply to my project?▼

Standards resolve in order: the AGENT.md chain from the target path up to the repo root, then project rules, then project skills, then the plugin's matching skill. The first source that speaks wins.

When should I use path-based improvement instead of a diff review?▼

Use it when you want to clean up or audit existing code that is not part of current changes. If you need to review a branch diff, commit, PR, or push, use the milestone review workflow instead.