agentleFS
wheeloswheelos/apollo-lite/.agents/skills/test-impact-analysis/SKILL.md

test-impact-analysis

Skill177 starsChanged 7 days agoApache-2.0View on GitHub

Select required validation from a diff, affected contracts, and risk. Use for test planning, regression selection, and determining sufficient evidence before implementation.

The file

Files
SKILL.md

Test Impact Analysis

Procedure

  1. Identify changed behavior, direct consumers, state ownership, configuration, and failure/degradation contracts from source and existing tests.
  2. Consult the test strategy and verified command registry. Reuse existing tests before adding tooling.
  3. Map each affected invariant to the smallest check that can actually refute an incorrect implementation. Record required evidence before editing. Formatting is not behavior evidence; open-loop output comparison is not closed-loop behavioral proof.
  4. For fixes, select a case detecting the original defect and nearby relevant boundaries. For migrations, cover direct producers and consumers. Escalate only when local evidence cannot cover the affected contract.
  5. Classify each required check as passed, failed, blocked, skipped, or not run. Record uncovered risks; never convert a missing fixture or non-triggering scenario into success.

Acceptance and failure handling

Deliver a compact change-to-evidence mapping with verified targets, environment, and any approval requirements. Stop when every required claim has sufficient evidence, not when the cheapest check passes. Do not install tools, modify assertions, or run road/HIL tests to resolve a planning gap without approval.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.