skills.rest
axiomantic
axiomanticOFFICIAL
Explore all skills by this author →
GitHub

fixing-tests

Identify, analyze, and repair failing tests without modifying production code.

8|5|Updated Dec 30, 2025
Search Tags:#debugging#ci-cd#quality-assurance#test-automation#test-debugging#fixing-tests
One-click install
npx skills add https://github.com/axiomantic/spellbook --skill fixing-tests
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fixing-tests
Source: https://github.com/axiomantic/spellbook/tree/main/skills/fixing-tests
Command: npx skills add https://github.com/axiomantic/spellbook --skill fixing-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies, analyzes, and repairs failing tests to keep software quality high without modifying production code.

Core Features & Use Cases

  • Detects and triages failing tests from logs and outputs.
  • Guides deterministic, minimal fixes and verification steps.
  • Use Case: When flaky tests or incorrect assertions cause instability, apply targeted fixes and re-run the suite to confirm green results.

Quick Start

Run the tests, inspect failures, and apply a minimal, deterministic fix that brings the suite green.

Frequently Asked Questions about fixing-tests

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

FAQPage Schema
How do I fix failing tests without modifying production code?▼

Fix failing tests by analyzing test outputs to identify incorrect assertions or flaky logic, then applying targeted repairs to stabilize the suite. This ensures software quality without modifying production code.

Why do flaky tests cause CI pipelines to fail and how can I stabilize them?▼

Flaky tests cause CI pipelines to fail due to inconsistent test automation logic or timing issues. You can stabilize flaky tests by applying deterministic, minimal fixes and re-running the suite to confirm green results.

Can I use this approach to triage test failures from local development logs?▼

Yes, you can triage test failures from local development logs by detecting and analyzing test outputs. The process guides deterministic fixes and verification steps to bring your local test suite green.

What is the best way to debug failing assertions in test automation?▼

The best way to debug failing assertions is to detect and triage failures from test outputs, then apply minimal deterministic fixes to the test logic. Run the test command to verify the repairs and achieve green results.

Does fixing tests involve running the test command to verify the repairs?▼

Yes, fixing tests involves running the test command to verify applied fixes. This ensures the test suite returns green results and records the outcomes while flagging any production bugs discovered during the process.

When should I not use test debugging for failing test suites?▼

You should not use test debugging to alter application behavior. The approach is limited to repairing failing tests and incorrect assertions without touching production code, even when flagging discovered production bugs for separate resolution.

Related Skills

Explore More Software Engineering Skills→
dzackgarzadzackgarza

test-coverage

Audit lattice-method test coverage against formal checklists and TEST_QUALITY.md criteria.

Community
Intermediate
OzeroHAXOzeroHAX
32

docs-report-test-reporting

Generate test reports summarizing executed tests, results, and discovered issues.

Community
Basic
CENKSSSCENKSSS

test-automation-strategy

Design test automation frameworks and integrate CI/CD pipelines.

Community
Advanced
drndrn
23

bisect

Identify the Git commit that introduced a bug using git bisect.

Community
Advanced