fix-loop
Fix Loop
Autonomous review-fix cycle that iterates until all critical issues are resolved.
The value of this skill is that it separates finding problems from fixing them. First review in a read-only, disconfirming posture. Then apply minimal targeted fixes. Do not rationalise away findings because you are about to edit the code.
Input
One of:
- File path(s) to review
- Directory to scan
- No argument — automatically determines scope
Execution
Step 1: Determine Scope
Determine which files to review, in priority order:
More from channingwalton/skills
software-development
Software development based on Extreme Programming (XP). Use it when implementing software features of any kind. Coordinates planning, TDD, refactoring, and commits.
3chatter
Use when the user asks you to start, join, or continue a conversation with other agents via chatter, agent-chat, or talking to other agents about X.
2fixer
Fixes critical code review findings. Receives review findings, applies targeted fixes, and verifies tests pass. Used by the fix-loop skill.
1retrospective
Use at the end of a session when the user asks how it went, what could be improved, how well the skill worked, or says "retrospective" / "retro" / "what did we learn". Surfaces gaps in the skill under examination and proposes targeted edits to fix them.
1code-reviewer
Autonomous code review agent. Use proactively after code changes to analyse for best practices, security, performance, and potential issues. Use when the user asks for a code review.
1