fix-solution

Automate iterative test-and-fix loops for benchmark problems across checkpoints.

138|30|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/SprocketLab/slop-code-bench --skill fix-solution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-solution
Source: https://github.com/SprocketLab/slop-code-bench/tree/main/.claude/skills/fix-solution
Command: npx skills add https://github.com/SprocketLab/slop-code-bench --skill fix-solution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams through an automated, iterative loop to test, identify, and repair failing solutions in benchmark problems until all tests pass.

Core Features & Use Cases

  • Automated evaluation cycle: run initial checks, analyze failures, apply minimal fixes, and re-run evaluations.
  • Cross-checkpoint propagation: propagate fixes to future checkpoints to maintain consistency.
  • Guardrails: keep fixes minimal and ask for user guidance if tests seem incorrect.

Quick Start

Invoke the fix-solution workflow with a snapshot path, problem name, and checkpoint index to begin iterative testing and repair.

Frequently Asked Questions about fix-solution

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

FAQPage Schema
How do I automate debugging and fixing failing benchmark solutions until tests pass?

Automated iterative debugging applies a test-and-fix loop that runs initial evaluations, analyzes failures, and makes minimal changes to benchmark solutions until tests pass. It re-runs evaluations after each repair to confirm the outcome.

What happens when a fix is applied to a failing solution at one checkpoint?

Cross-checkpoint propagation applies fixes made at one checkpoint to future checkpoints to maintain consistency across the benchmark. This ensures repairs remain valid as the solution progresses through iterative testing.

Does the iterative test-and-fix workflow require any external dependencies or libraries?

No external dependencies are required to run the iterative test-and-fix workflow. The process operates independently to evaluate failures, apply minimal changes, and re-run evaluations without needing additional libraries.

What is the best way to handle incorrect tests during automated failure analysis?

During failure analysis, guardrails keep fixes minimal and prompt for user guidance if tests seem incorrect. This prevents the workflow from overwriting or bypassing test logic that may contain intentional validation rules.

How do I start an automated evaluation cycle for a specific benchmark problem?

Invoke the workflow with a snapshot path, problem name, and checkpoint index to begin the automated evaluation cycle. The system will run initial checks, analyze failures, and iteratively apply minimal fixes.

Why does my solution keep failing after applying minimal changes to the checkpoints?

If solutions keep failing, the failure analysis mechanism may identify that tests themselves are incorrect and prompt for user guidance. The disciplined workflow ensures changes remain minimal to avoid introducing new errors.