Loading...
Loading...
Found 55 Skills
Use after run-plan completes to independently verify the implementation. Reads only the plan document and inspects the codebase from scratch — information-isolated from the execution context. Produces a structured review document with PASS/FAIL verdict. Triggers when the user says "review the work", "verify the implementation", "check if the plan was executed correctly".
Iteratively fix test failures until all tests pass. Use when tests are failing and you want Claude to automatically plan and fix them in a loop.
Use when completing implementation, fixing bugs, refactoring code, or any time you need to verify the test suite passes. Also use when tests fail and you hear "pre-existing" or "not my changes" — enforces strict code ownership.
Use when you need to generate `{FEATURE_DIR}/verification/report-{date}-{version}.md` (test report) during the verification phase of Spec Pack, provide deliverable conclusions that are traceable to test cases and defect references.
Test execution patterns, failure classification, and result analysis
Apifox CLI Usage Check and Version Verification: Use this when the command succeeds but the resource isn't visible on the Apifox page, the resource can't be found via list/get after creation, test execution fails, reports are missing, agentHints/help/actual behavior are inconsistent, or you suspect the local CLI version isn't up-to-date.
Execute Tests - walks through test cases from the test plan, collects results, and updates the plan. Use when verifying a feature implementation.