One-click install
npx skills add https://github.com/satish-krishna/sigil --skill auto-fixer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-fixer
Source: https://github.com/satish-krishna/sigil/tree/main/.claude/plugins/bob/skills/auto-fixer
Command: npx skills add https://github.com/satish-krishna/sigil --skill auto-fixer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces a rigorous, test-driven workflow for fixing a single quality finding, ensuring that every change is preceded by a failing test and a minimal, well-audited implementation.

Core Features & Use Cases

  • Test-first fixes: Write the failing test before implementing the fix to prevent regressions.
  • End-to-end automation: Validate the finding, implement a minimal fix, run tests, and prepare a PR with an audit trail.
  • Campaign support: Works within the Bob quality orchestrator and via the /bob:fix trigger to streamline software-quality improvements.

Quick Start

Trigger the auto-fixer on a selected finding to run the red-green-refactor cycle and create a PR.

Frequently Asked Questions about auto-fixer

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

FAQPage Schema
How do I automate fixing code quality findings with test-driven development?

Automating test-driven development for quality findings requires writing a failing test before implementing a minimal fix. This skill validates the finding, enforces the red-green-refactor cycle, runs the test suite, and pushes a PR with an audit trail.

How does test-driven automation prevent regressions when applying code fixes?

Test-driven automation prevents regressions by enforcing a failing test before any implementation. It validates the quality finding, writes the test, applies a minimal fix, and runs the full test suite to ensure no existing functionality breaks before pushing a PR.

Can I use automated code fixes within a quality orchestrator campaign?

Yes, automated code fixes work within the Bob quality orchestrator campaign. Triggered by the /bob:fix command or orchestrator, the skill processes a single finding object to generate a targeted, auditable PR that fits seamlessly into broader software-quality campaigns.

What is the best way to ensure a minimal and auditable fix for a single quality finding?

The best way to ensure a minimal and auditable fix is using a strict test-driven workflow. This skill validates the finding, writes a failing test, implements the smallest change necessary, and pushes a pull request containing a full audit trail of the process.

Do I need to trigger fixes one at a time for each quality finding?

Yes, the automated fixer processes a single quality finding per run to maintain strict test-driven compliance. By isolating each finding, it validates the issue, writes a targeted failing test, and pushes a dedicated PR, ensuring the fix remains minimal and auditable.