attack-tests
/attack-tests
Attack an implemented change with adversarial tests and mutation checks. Use for assigned test work after implementation, within the tester role scope.
- Author
- jisuzzzz ↗
- Repository
- haechi ↗
- Licence
- MIT
- Last repository change
- 11.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Attack an implemented change with adversarial tests and mutation checks. Use for assigned test work after implementation, within the tester role scope.
Original author description
Attack an implemented change with adversarial tests and mutation checks. Use for assigned test work after implementation, within the tester role scope.
How it works
- Task boundary
- Procedure
SKILL.md preview
--- name: attack-tests description: Attack an implemented change with adversarial tests and mutation checks. Use for assigned test work after implementation, within the tester role scope. --- # attack-tests Apply the [common work contract](../../principles/work-contract.md) within this task’s scope. It owns applicable pre-action evidence, product implementation obligations and completion requirements; this skill supplies the method. Current common guidance already delivered or read may be reused. ## Task boundary You are spawned after the implementation is done. The happy path is what the implementer built for; your job is to find inputs and states that break it, and to make sure the tests would notice. Keep happy-path tests to one per spec point at most. Edit only the test files you are assigned and shared test fixtures the task allows. Never change source to make a test pass, and never weaken an assertion to match a bug. When a test exposes a bug, confirm it fails once, then record it the way AGENTS.md says (if it says nothing, a skipped test whose name starts with `BUG:` and states the expected behavior) — failing tests are never left in the files. The orchestrator decides whether the bug is fixed now or filed. ## Procedure Attack sibling paths first — every real bug this role has found so far had that shape. Use the sibling path map, then the general weak points: empty, null and boundary values; loading, error and empty-list states; repeated or rapid interaction; out-of-order or failed responses; permission combinations; long or unusual input; teardown during async work; stale cache after a write. For order-dependent, concurrent or flaky failures, optional probes are in `<haechi tools>/../skills/bug/references/investigation.md`, using the tools path from the task's repo facts. Choose one when useful; do not add sleeps or weaken assertions to obtain a passing run. Then run the mutation check on the changed source with the tests that cover it. You change existing tests in exactly two cases: a mutant survived (tighten an assertion or add a case), or a test is tied to internals (rewrite it to assert what a user of the code observes). Leave every other test alone. Each new test must catch a different mutant or path. Tests are deterministic: fixed time and randomness, network only through the repo's mocking setup, synthetic fixtures only. Run only your test files with the repository's single-test command, never the forbidden whole-repo commands. Never commit, stash, checkout or reset. Report: test files, cases attacked, bugs found (what each shows, and which sibling pair if it is that shape), mutants killed, survived and equivalent before and after, open questions for behavior the spec does not define.
Versions
The database has no other skills named attack-tests.
Database snapshot: 13.11.2026 · package version 51a2cffb2836 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95go-table-driven-tests
Write Go table-driven tests following established patterns. Use when writing tests, creating test functions, adding test cases, or when the user mentions "test", "table-driven", "Go tests", or testing in Go codebases. - 100adversarial-tester
Use after completing an implementation to find unknown failure modes. Reads the implementation diff and writes up to 5 tests designed to make it break — per-task, scoped to that single implementation (for a fully-assembled multi-component feature, use inquisitor to hunt… - 86attack
Adversarial review of a change to automation code. Three parallel reviewers try to break it through trust and injection, failure and rerun, and contract changes, and a finding survives only if a run demonstrates it. Use for "attack this" or "adversarial review", and before… - 100running-mutation-tests
Execute mutation testing to evaluate test suite effectiveness. Use when performing specialized testing. Trigger with phrases like "run mutation tests", "test the tests", or "validate test effectiveness". - 100rein-test
Use this skill when asked to run tests, before committing, or for Tier 3 releases. Runs the project's real test command by default; --generate dispatches the headless test_engineer Tester (Claude, sonnet) to write tests; --fast runs the Tester on haiku; --vibe triggers the… - 100running-mutation-tests
Execute mutation testing to evaluate test suite effectiveness. Use when performing specialized testing. Trigger with phrases like "run mutation tests", "test the tests", or "validate test effectiveness".