Drive the card's Review Hero loop by hand — trigger a review, address its comments, rerun until clean, then merge. Use in an external tool (Claude Code, Cursor) where Workhorse's automated loop isn't running.
中文简介正在准备中。当前显示原文说明。
39 个(beyondessential 的仓库) · 按人气排序
Drive the card's Review Hero loop by hand — trigger a review, address its comments, rerun until clean, then merge. Use in an external tool (Claude Code, Cursor) where Workhorse's automated loop isn't running.
中文简介正在准备中。当前显示原文说明。
Produce a release test-impact analysis for a Tamanu version upgrade: compare two Tamanu releases and classify every functional area as Full Test, Smoke Test, or Skip, each with a short reason and the Linear card or PR reference. Use when the user wants a test plan, QA scope, regression scope, or "what to test" for a Tamanu release or upgrade, wants to compare or diff two Tamanu versions (e.g. v2.57 to v2.59), or asks which areas changed between two releases. Handles Tamanu's train-release model (release/X.Y branches vs vX.Y.Z tags) and maps changed files and PRs to Tamanu functional sections (Patient Management, Encounters/Charting, Surveys & Programs, Medications, Labs, Imaging, Appointments, Vaccinations, Sync, Settings, Reports, Admin/Permissions, Mobile, etc.). Optionally maps against a regression-testing spreadsheet's sections when one is provided.
中文简介正在准备中。当前显示原文说明。
Review implementation for common security vulnerabilities
中文简介正在准备中。当前显示原文说明。
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
中文简介正在准备中。当前显示原文说明。
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
中文简介正在准备中。当前显示原文说明。
Check upgrade safety for a Tamanu upgrade that spans many versions: verify that every intermediate hotfix is included in the target version, and surface the new configuration/settings, data migrations, and FHIR rematerialisation impact the upgrade brings. Use when the user wants to check an upgrade from one Tamanu version to another (e.g. "check hotfixes from v2.31 to v2.47"), confirm no intermediate hotfix was dropped, or understand what config, migrations, and FHIR rework a multi-version jump requires. 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 cutting a release (see release-cutoff-checks) or deciding which tests to run (see scope-tamanu-release-tests).
中文简介正在准备中。当前显示原文说明。
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
中文简介正在准备中。当前显示原文说明。
Generate a context-rich briefing prompt for an external agent (Claude Code, Cursor, etc.)
中文简介正在准备中。当前显示原文说明。
Interview me about this card to develop the acceptance criteria
中文简介正在准备中。当前显示原文说明。
Produce an HTML mockup for the UI being discussed
中文简介正在准备中。当前显示原文说明。
Draft edits to existing specs (or a new spec if no existing one fits) from the card description
中文简介正在准备中。当前显示原文说明。
Update npm/yarn/pnpm dependencies using manifest-first, lockfile-aware workflows. Prefer declared version bumps over resolution overrides. Use when updating, upgrading, or patching dependencies; fixing transitive dependency versions; addressing npm audit or CVE findings; or removing stale overrides.
中文简介正在准备中。当前显示原文说明。