fix

Apply minimal code fixes and validate with verifiers until tests pass.

5|2|Updated Nov 17, 2025
One-click install
npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill fix-outlinedriven
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/OutlineDriven/odin-gemini-cli-extension/tree/main/skills/fix
Command: npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill fix-outlinedriven

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Polymorphic iterative repair loop that handles verifier failures, structured findings, or user-provided bug descriptions, enabling automated patches with verification-driven keep/revert cycles.

Core Features & Use Cases

  • Iterative patch application: apply minimal fixes, commit checkpoints, and verify impact.
  • Verifier-driven validation: run repo-native verifiers and guard commands to ensure regressions are detected early.
  • Triage-ready workflow: can route to gh-fix-ci or gh-address-comments based on PR and authentication context.

Quick Start

Start a fix session on the current repository, describe the failure context, and let the system patch, verify, and revert as needed until the tests pass.

Frequently Asked Questions about fix

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

FAQPage Schema
How do I automate code repair for failing CI tests?

Automated code repair for failing CI tests applies minimal fixes iteratively and validates them with repo-native verifiers until the test suite passes. It commits checkpoints during patching and automatically reverts changes if guard checks detect regressions.

What is an iterative fix loop and how does it handle flaky tests?

An iterative fix loop handles flaky tests by applying minimal patches, running verifiers, and deciding whether to keep or revert the code changes. This cycle repeats automatically until verifiers pass and guard commands confirm no regressions were introduced.

How do I fix code from a bug report using automated verification?

Fixing code from a bug report using automated verification involves providing the bug description as input so the system can patch the code and validate the changes. The system applies iterative fixes and uses verifiers to ensure the patch resolves the issue without regressions.

Can I limit the number of automated patching attempts during a fix loop?

Yes, you can limit automated patching attempts by using configuration cap overrides. This allows you to set a maximum threshold for the iterative fix cycles and also specify mode overrides to tailor the repair workflow to your specific repository constraints.

Does the automated fix workflow support routing to CI or PR comment handlers?

The automated fix workflow supports triage-ready routing to gh-fix-ci or gh-address-comments based on the PR and authentication context. This allows the iterative repair loop to transition seamlessly into specialized CI failure or pull request comment resolution tasks.