What is test-refactoring?

A test-suite cleanup process that removes duplicate or unnecessary tests while checking that previously covered code remains covered.

Use it to consolidate tests, combine repeated cases, remove dead coverage, and address complaints about having too many tests.

Large test suites can be slow, repetitive, and difficult to maintain. Deleting the wrong test can leave parts of the code untested, so this process protects coverage while reducing overlap.

How haakonbull/autosprint configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to haakonbull/autosprint. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/haakonbull/autosprint/master/.claude/skills/test-refactoring/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/haakonbull/autosprint

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/haakonbull/autosprint/test-refactoring/github.svg)](https://agentmods.dev/skills/haakonbull/autosprint/test-refactoring)

Your own site

<a href="https://agentmods.dev/skills/haakonbull/autosprint/test-refactoring"><img src="https://agentmods.dev/badge/skills/haakonbull/autosprint/test-refactoring/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/haakonbull/autosprint/test-refactoring"><img src="https://agentmods.dev/badge/skills/haakonbull/autosprint/test-refactoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,586 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00062	$0.01586
Opus 5	$0.00031	$0.00793
Sonnet 5	$0.00012	$0.00317
Haiku 4.5	$0.00006	$0.00159

Measured 9d ago against content hash 7a34e2021931, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

test-refactoring scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/test-refactoring/SKILL.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Refactor the marked tests (or the current test file if nothing is marked) following these rules. This skill is distinct from python-refactoring because the dominant operation here is deletion — not restructure, not rename — and deletion in tests has a failure mode that restructuring in production code doesn't: silently losing coverage.

The load-bearing invariant

Coverage must not decrease. If any executable line that was covered before is uncovered after, the refactor has failed, regardless of how many tests you consolidated or how clean the new code looks. This is not a soft preference — it's the only thing separating "good test consolidation" from "I deleted tests that were actually guarding something."

Preflight

Before touching any test, establish a baseline:

Run pytest --cov=<pkg> --cov-report=json -m "not slow" (substitute the project's real package path and marker). Save the resulting coverage.json to a temp location.
Note the passing test count. It must match exactly at the end.
If coverage cannot be measured (project has no coverage tooling configured, or --cov fails), STOP and tell the user. Do not refactor tests in a project where coverage drift can't be verified — the invariant is untestable, and you're gambling.

Rules for deleting a test

A test may be deleted only if all of these hold:

A surviving test subsumes its coverage. You must name the surviving test by file + function name in the RESULT summary (e.g. "deleted test_foo::test_basic_case (subsumed by test_foo::test_parametrised_cases)"). Vague claims like "the smoke tests cover this" are not acceptable — name the test.
The surviving test asserts the same outcome, not just exercises the same code path. Two tests that both call build_report() but one checks the manifest and the other checks the filesystem layout are NOT redundant — they guard different contracts.
Same-fixture is not evidence of overlap. Two tests using the same tmp_path fixture can still be guarding entirely different invariants. Overlap must be proven at the assertion level.
The test is not the sole guard on a branch. If deleting it would drop coverage on any line, it stays — even if it looks cosmetically similar to another test. The coverage report is the final arbiter.

Read the full file on GitHub · 87 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago First seen · 87 lines · 62 tokens per session scan A 7a34e2021931

Subscribe to this mod's changes

test-refactoring is a skill published in the GitHub repository haakonbull/autosprint (5 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 1,586 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

autosprint: Skill for Claude Code