test-fixing

Group test failures by error type and module, then fix and re-run tests.

2|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/ShunmeiCho/dotclaude --skill test-fixing-shunmeicho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-fixing
Source: https://github.com/ShunmeiCho/dotclaude/tree/main/skills/test-fixing
Command: npx skills add https://github.com/ShunmeiCho/dotclaude --skill test-fixing-shunmeicho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams systematically identify and fix failing tests by applying smart error grouping, reducing debugging time and increasing reliability.

Core Features & Use Cases

  • Initial Test Run: Run make test to surface all failing tests and error output.
  • Smart Error Grouping: Group failures by error type, module/file, and root cause to prioritize fixes.
  • Systematic Fixing Process: For each group, identify root cause, implement minimal fixes, verify by re-running tests, and move to the next group.

Quick Start

Run make test to surface failures, then follow the recommended workflow to group and fix errors.

Frequently Asked Questions about test-fixing

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

FAQPage Schema
How do I group failing pytest tests by error type to fix them faster?

To fix failing pytest tests faster, group test failures by error type, module, and root cause. This smart error grouping helps prioritize fixes and systematically resolve each failure group through minimal code changes and re-running the suite.

What is the best way to debug multiple failing tests at once?

The best way to debug multiple failing tests is to apply smart error grouping after running your test suite. Grouping failures by root cause allows you to implement minimal fixes for each group and verify them by re-running tests until all groups pass.

How do I use make test to surface and group test failures?

You can run make test to surface all failing tests and error output. Once failures are surfaced, group them by error type and module to identify the root cause, implement minimal fixes, and verify by re-running the tests.

Does smart error grouping work for any software project test suite?

Smart error grouping is applicable across software projects to reduce debugging time and ensure test suites pass. It follows a systematic workflow of running tests, grouping failures, implementing minimal fixes, and re-running tests until all groups pass.

Why should I group test failures before implementing fixes?

Grouping test failures before implementing fixes reduces debugging time and increases reliability. By categorizing failures by type and module, you can identify root causes, apply minimal fixes to each group, and systematically verify them through re-running the test suite.