automate-repair

Name: automate-repair
Availability: InStock
Author: NESNILNEHC

Automate iterative code review, testing, and targeted fixes to converge a repository to green.

7|3|Updated Jan 23, 2026

Search Tags:#automation #testing #diff #patch #code-review #repair

Ready to run

npx skills add https://github.com/nesnilnehc/ai-cortex --skill automate-repair

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: automate-repair
Source: https://github.com/nesnilnehc/ai-cortex/tree/main/skills/automate-repair
Command: npx skills add https://github.com/nesnilnehc/ai-cortex --skill automate-repair

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Iterative code review, testing, and targeted fixes to converge a repository to a green state, reducing wasted cycles and surfacing blockers early.

Core Features & Use Cases

Automated, bounded review-test-fix cycles that minimize patch size and preserve contracts.
Evidence-driven iterations that prioritize the most impactful failing signal and re-run tests after patches.
Structured repair-loop reporting that documents commands, patches, and remaining risks for stakeholders.

Quick Start

Instruct the agent to run a repair loop on the target repository using default scope and fast mode to converge tests to green.

Frequently Asked Questions about automate-repair

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

FAQPage Schema

How do I automate code review and testing to fix failing tests?▼

Automating code review and testing involves running an iterative repair loop that applies targeted fixes to a repository until tests pass. This minimizes patch size, prioritizes impactful failing signals, and re-runs tests after patches to converge to a green state.

What is an automated repair loop for getting a repository to a green state?▼

An automated repair loop is a bounded cycle of code review, testing, and targeted fixes applied to a repository. It uses evidence-driven iterations to run tests in fast, CI, or full modes, applying minimal patches until tests converge to a green state.

How do I run iterative test-fix cycles with minimal patches on a codebase?▼

Running iterative test-fix cycles requires applying bounded, evidence-driven iterations that prioritize the most impactful failing test signal. The agent applies minimal patches to the codebase, re-runs failing tests after each patch, and generates structured reports for stakeholders.

Can I run automated repair loops using fast, CI, and full test modes?▼

Yes, automated repair loops support running tests in fast, CI, and full modes. This allows the repair process to reconcile diffs or codebases efficiently by selecting the appropriate test scope while applying minimal, auditable fixes during each iteration.

Does the automated repair loop stop after a bounded number of iterations if tests fail?▼

Yes, the automated repair loop enforces bounded iterations to prevent infinite cycles. If tests still fail after reaching the iteration limit, it stops and provides structured repair-loop reporting that documents commands, applied patches, and remaining risks for stakeholders.

Why should I use an automated repair loop instead of manually patching failing tests?▼

Using an automated repair loop instead of manually patching failing tests reduces wasted cycles and surfaces blockers early. It enforces evidence-driven iteration and structured reporting, ensuring fixes are minimal, preserve contracts, and are fully auditable for stakeholders.