acceptance-audit
FreeCheck whether this card's code meets the acceptance criteria
The English summary is being prepared. Showing the original description.
beyondessential/tamanu9Updated Oct 20, 2026
FreePublished on GitHub
automate-test-cases
Write automated tests for unticked scenarios in this card's test cases
The English summary is being prepared. Showing the original description.
See how to installFiles included (1)
- SKILL.md1.6 KB
SKILL.md (original)
Review the instructions the agent will receive before you install.
Your task: Automate test cases
If you don't already have this card's context (title, identifier, description) — for instance when running outside Workhorse — establish it first by following .agents/docs/card-context.md.
Write automated tests that match the unticked scenarios in this card's test-cases file, ticking each item as its matching test lands.
- Read the test-cases file at
.workhorse/test-cases/{card-id}/. If no file exists, stop and ask the user whether to runDraft test casesfirst - For each unticked scenario, locate the right place to put its automated test — follow the target repo's existing test conventions (framework, file layout, fixtures)
- Write the test so it exercises the scenario as stated. If the scenario cites a spec id, the test is the automation of that acceptance criterion — match its intent
- Tick the scenario (
- [ ]→- [x]) once its test is written and passing locally. Update the test-cases file in place - If a scenario is genuinely not automatable (manual feel, cross-browser visual), leave it unticked and note in the file why it's manual-only
- Summarise what you automated, which scenarios remain manual, and any scenarios you couldn't make sense of
See specs/test-cases/overview.md for the file's shape.
Reviews
No reviews yet. Tell others what you thought.
Comments
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
More skills from this repository
Summarise the unit and e2e tests a branch/PR adds, run only those, and produce a paste-ready report (e.g. for a Linear card). Use when asked to 'summarise added tests', 'run the new tests', 'what tests did this PR add', or to prove a card's test coverage.
The English summary is being prepared. Showing the original description.
beyondessential/tamanu9Updated Oct 20, 2026
ascii-design
FreeRun a quick UX/UI workshop using ASCII-art sketches
The English summary is being prepared. Showing the original description.
beyondessential/tamanu9Updated Oct 20, 2026
bug-review
FreeReview code changes on this card for likely bugs, regressions, and missed edges
The English summary is being prepared. Showing the original description.
beyondessential/tamanu9Updated Oct 20, 2026
Maintain a support docs pack — dedup, length budgets, and no splintering — and land changes as a reviewed pull request. Use when a support thread, or a hand-off from Support assist, surfaces a new resolution, a correction to an existing one, or a deployment quirk worth recording. Not for ordinary code changes.
The English summary is being prepared. Showing the original description.
beyondessential/tamanu9Updated Oct 20, 2026
design-audit
FreeAudit this card's mockups or implementation against the design library
The English summary is being prepared. Showing the original description.
beyondessential/tamanu9Updated Oct 20, 2026