Axidify Test
Discover commands
From package.json scripts, Makefile, README, or CI config — find:
- Unit / integration test command (e.g.
pnpm test,pytest,go test ./...) - E2E command if present (e.g.
playwright test)
Run what matches the user's scope. Prefer subset when scope is narrow:
pytest path/to/test_file.py::test_namepnpm vitest run path -t "name"go test ./pkg/... -run TestName
Automated tests
- Locate tests related to the scope
- Run the appropriate command
- Report: passed / failed / skipped
- For failures: file, test name, likely cause
- Propose fixes only if failures relate to recent changes or the user asked
Flaky / snapshots
- Flaky: note retry behavior from config; do not delete tests to greenwash
- Snapshots / goldens: update only when the user approves intentional output changes
When tests are thin or missing
- Trace main code paths for the feature
- Note gaps: untested branches, missing validation
- Suggest concrete tests worth adding (behavior, not trivial asserts)
Rules
- Do not delete or skip tests to greenwash unless the user agrees
- Prefer the project's existing test runner and conventions
Related skills
- implement — fix failures from your changes
- debug — when failures need root-cause analysis
- ci — CI-only failures or environment mismatch
- ui-browser-check — visual issues better verified in the browser