查找技能

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.

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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.

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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).

中文简介正在准备中。当前显示原文说明。

Draft or refine the test-cases checklist for this card

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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.

中文简介正在准备中。当前显示原文说明。

Diagnose and fix the bug described on this card

中文简介正在准备中。当前显示原文说明。

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).

中文简介正在准备中。当前显示原文说明。

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).

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

Start a working doc — a drafting space where spec-level and implementation thinking co-exist before splitting into specs, plan, and test cases

中文简介正在准备中。当前显示原文说明。

Workshop the technical approach and capture notes in the plan

中文简介正在准备中。当前显示原文说明。

Workshop this idea with me

中文简介正在准备中。当前显示原文说明。

Review this card's specs with fresh eyes for gaps, contradictions, and cross-spec impact

中文简介正在准备中。当前显示原文说明。

Split a working doc into the card's specs, plan, and test cases once its shape is clear

中文简介正在准备中。当前显示原文说明。

Produce or refine a project-level mockup illustrating a section of the PRD

中文简介正在准备中。当前显示原文说明。

Workshop the shape of this project — audience, components, ambiguities — before drafting the PRD

中文简介正在准备中。当前显示原文说明。

Check whether this card's code meets the acceptance criteria

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

Rebase onto latest upstream, checking for soft conflicts

中文简介正在准备中。当前显示原文说明。