Browse skills

Fresh-eyes review of the project's PRD for gaps, contradictions, vague phrasing, and unresolved decisions

The English summary is being prepared. Showing the original description.

Workshop this idea with me

The English summary is being prepared. Showing the original description.

Run a quick UX/UI workshop using ASCII-art sketches

The English summary is being prepared. Showing the original description.

Workshop how to break this card into smaller spawned cards and capture entries in the card breakdown

The English summary is being prepared. Showing the original description.

Implement this card

The English summary is being prepared. Showing the original description.

Review the product engineer's post-implementation testing notes for how thoroughly they cover the card's requirements and risk, and whether regression-worthy cases are automated at the right level of the test hierarchy

The English summary is being prepared. Showing the original description.

Run a support investigation as a suggest-and-interpret loop, never executing anything yourself — orient to the product's support pack and follow the signal with judgment. Use when someone asks for help triaging, investigating, or resolving an operational or support issue on a deployment. Not for feature-development cards (see investigate-and-fix and implement-this).

The English summary is being prepared. Showing the original description.

Check whether this card's code meets the acceptance criteria

The English summary is being prepared. Showing the original description.

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.

Write automated tests for unticked scenarios in this card's test cases

The English summary is being prepared. Showing the original description.

Review code changes on this card for likely bugs, regressions, and missed edges

The English summary is being prepared. Showing the original description.

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.

Audit this card's mockups or implementation against the design library

The English summary is being prepared. Showing the original description.

Draft or refine the project's PRD from the description and conversation

The English summary is being prepared. Showing the original description.

Draft public Tamanu release notes for a given version. Use when the user wants release notes for a Tamanu release (e.g. "draft release notes for v2.45"). Pulls work from the specs and code that landed in that version's release/X.Y branch, plus the matching issues in the trackers (Linear's Tamanu team and Workhorse's Tamanu workspace), reconciles them, and writes docs/release-notes/vX-YY.md in the canonical v2.44 format for project managers and system administrators, plus a styled HTML rendering at .workhorse/design/designs/vX-YY-release-notes.html. Not for developer changelogs or QA test scoping (use scope-tamanu-release-tests for the latter).

The English summary is being prepared. Showing the original description.

Draft or refine the test-cases checklist for this card

The English summary is being prepared. Showing the original description.

Pull remote changes and reconcile with local work, checking for soft conflicts

The English summary is being prepared. Showing the original description.

Rebase onto latest upstream, checking for soft conflicts

The English summary is being prepared. Showing the original description.

Run a live investigation as an operator-driven query loop: the operator runs each query on the live system and pastes the result back, and you guide the investigation one labelled query at a time. Use alongside support-assist (which covers what to investigate) whenever someone is pasting query or command output back from a deployment, especially during an incident. Covers labelling, pacing, making each query decide the next step, version-grounding, and keeping queries cheap and correctly classified.

The English summary is being prepared. Showing the original description.

Diagnose and fix the bug described on this card

The English summary is being prepared. Showing the original description.

Draft or refine the implementation checklist from specs and current code

The English summary is being prepared. Showing the original description.

Run Tamanu pre-release verification checks: verify that hotfixes on the current release branch are merged forward to main, and that hotfixes from prior release branches are included in the current release. Use when the user wants to run "pre-release checks", verify hotfix integrity before cutting or shipping a Tamanu release, confirm a release/X.YY branch is safe to release, or check that no hotfix has been orphaned (left on neither main nor the current release). Handles Tamanu's train-release model (release/X.YY branches vs vX.YY.Z patch tags) and the cherry-pick model where the same logical fix has different SHAs on different branches. Purely git-based — no live database or Canopy access needed. Not for deciding which tests to run (see scope-tamanu-release-tests).

The English summary is being prepared. Showing the original description.

Rebase the branch past a merge so a follow-up PR carries only new work

The English summary is being prepared. Showing the original description.

Run the Tamanu release-branch CUTOFF checks when preparing to cut a new release/X.YY branch: confirm the previous release's hotfixes are merged to main, reconcile the commits since the previous release against the "Merged to main" card list from Linear, and scan for data/reporting/schema changes. Use when the user is cutting a Tamanu release and wants to verify the codebase is ready, wants to check main against the previous release branch, or wants to reconcile commits with a Linear "Merged to main" column (they should paste the card list). Handles Tamanu's train-release model (release/X.YY branches vs vX.YY.Z patch tags) and the cherry-pick model where the same logical fix has different SHAs on different branches. Purely git-based — no live database or Canopy access needed. Not for verifying an existing release branch's hotfix integrity (see pre-release-checks) or for deciding which tests to run (see scope-tamanu-release-tests).

The English summary is being prepared. Showing the original description.