Use for writing tests, designing test coverage, handling defect fixes, root-cause analysis, CI verification, or configuring commit-time hooks. Also for creating test matrices or choosing between unit/integration/E2E tests, but not for general development or linting setup.
The exact command may vary by repository. Check the README on GitHub.
For the skill author
Drop this on your repo README
Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.
[](https://www.skillteca.com.br/skills/quality-workflow?utm_source=badge&utm_medium=readme&utm_campaign=badge)
One short email with only the new Automação skills. 4 minutes of reading, no spam, unsubscribe with one click.
You confirm your email on the first send. No spam. Unsubscribe with one click.
Quality workflow
Test coverage methodology
Tests MUST cover success, failure, boundary, invalid input, and
key state transitions (including first-run/cold-start vs
subsequent-run behavior when relevant). Tests MUST include
representative concurrency, retry, and recovery cases when
relevant.
For non-trivial changes, the agent MUST enumerate the changed
externally visible contract surface before choosing tests. Use
the changed docs, specs, CLI help, API descriptions, UI
co
[Description truncada. Veja o README completo no GitHub.]
