test-auto-fix
SolidDiagnoses failing tests across any project, classifies each failure as a test-bug, prod-bug, or unsure, confidence-gates the fix (auto-apply at >=90%, 80-89 ask, <80 escalate), applies it, and re-runs until green. Surface-driven: reads per-project configuration from a surface file keyed by normalised git remote URL. Bootstrap auto-detects the stack on first run and proposes a surface diff for user approval. Hard-refuses to delete tests, add .skip/.only, or weaken assertions. Regression-detects after every fix: reverts on new failure instead of stacking. Triggers on "fix my failing tests", "tests are red", "auto-fix tests", "heal the tests", "/test-auto-fix".
Install
Quality Score: 84/100
Skill Content
Details
- Author
- mthines
- Repository
- mthines/agent-skills
- Created
- 3 months ago
- Last Updated
- 2 days ago
- Language
- TypeScript
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
ci-auto-fix
Diagnoses a failed CI check, classifies it with an explicit verdict (code-bug | workflow-bug | dep-bug | env-bug | flaky | unsure), confidence-gates the fix (>=90 auto, 80-89 ask, <80 escalate), applies it, pushes, and iteratively verifies until CI passes — reverting the last commit if a brand-new failure appears. Provider-agnostic in scope; currently implements the GitHub Actions path via `gh`. Hard- refuses to disable, skip, or weaken checks. Triggers on "CI is failing", "fix the CI", "the build is red", "auto-fix this PR's checks", "GitHub Actions failed", "/ci-auto-fix".
fix-test
Auto-diagnose and fix failing tests — up to 3 attempts with re-runs. Triggers on: fix test, failing test, broken test, test error, why is this test failing, debug test.
tests
Fixes failing tests and lint/type errors, audits test-suite quality with a fleet of specialist reviewers, or drives coverage — for any project configured with a supermodo skills.config.json. Modes: `tests` (default) fixes every failure tier by tier (unit, integration, E2E, lint); `tests audit [scope]` spawns parallel specialist reviewers (spec-alignment, assertion-strength, corner-cases, coverage-balance, and a domain lens derived from the project's docs), runs mutation probes where configured, and adversarially verifies every finding with a second model before reporting; `tests coverage` drives coverage to the configured target with a balance check. Use whenever the user mentions failing tests, lint errors, "make tests pass", green build, flaky tests, test quality, weak or missing tests, corner cases, coverage, mutation testing, or asks whether the tests actually protect the core logic — even without "/tests".