القائمة
Full audit → fix → test → build → deploy → verify cycle for this repo. Auto-detects repo; captain-mode with verify-first + merge carve-outs.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Add a clinical rule to Toranot's src/engine/rules.ts with the Golden Rule invariant, unique group check, comfort-care suppression audit, and automatic test scaffolding. Use when user says "add a rule", "new rule", "add clinical rule", "new trigger in rules.ts", or when proposing a new auto-generated task pattern for the rules engine. DO NOT use for drug interactions (those live in drugSafety.ts).
Generate professional SZMC (Shaare Zedek Medical Center) ward clinical notes in exact institutional format. PRIMARY USE: geriatric and internal medicine ward admission notes (קבלה רפואית) and ward discharge summaries (סיכום שחרור / סיכום אשפוז זמני). Also supports ED discharge (סיכום שחרור מיון) as secondary use. Trigger on: "כתוב לי קבלה", "כתוב סיכום שחרור", "סיכום אשפוז", "draft a note", "format this admission", or when user uploads תיק אשפוז / EMR data / patient data. For geriatric ward notes, auto-runs Beers/STOPP-START/drug interaction analysis. Always generates HTML export for RTL copy-paste into EMR. Do not attempt ad-hoc formatting — always use this skill.
Auto-update SKILL.md (toranot-dev) with current ground truth. Run after every deploy or when skill feels stale.
End-to-end Toranot ship pipeline. Runs the mandatory 7-step workflow (tsc, vitest, vite build, README update, git push with PAT rotation, Netlify deploy verification, auditor sweep). Use when user says "push", "push Toranot", "deploy", "ship Toranot", "ship it", "release", or any variant asking to ship Toranot to production. DO NOT use for watch-advisor2 or Shlav A Mega — this is Toranot-specific.
End-to-end Toranot ship pipeline. Runs the mandatory 7-step workflow (tsc, vitest, vite build, README update, git push with PAT rotation, Netlify deploy verification, auditor sweep). Use when user says "push", "push Toranot", "deploy", "ship Toranot", "ship it", "release", or any variant asking to ship Toranot to production. DO NOT use for watch-advisor2 or Shlav A Mega — this is Toranot-specific.
Canonical format for Toranot `.cowork/<slug>.md` handoff files. Load whenever writing or reading a handoff. Enforces the five required sections and what belongs in each.
| name | source-command-audit-fix-deploy |
| description | Full audit → fix → test → build → deploy → verify cycle for this repo. Auto-detects repo; captain-mode with verify-first + merge carve-outs. |
Use this skill when the user asks to run the migrated source command audit-fix-deploy.
Run the audit-fix-deploy skill end-to-end for the repo in the current working directory.
Captain mode: ACT, don't ask — but obey the VERIFY-FIRST, GATES, CITATION, and MERGE rules below.
The skill owns the per-repo pipeline (STEP 0 detect → Audit → Fix → Test+Build → Deploy → Verify → Skill-update → Self-improve). Follow it; do not reinvent it. If it isn't already in context, load audit-fix-deploy + its deploy-primitives companion by name.
Start with STEP 0 immediately. Do not ask for confirmation.
git log -8 --all, read the live SW/version (curl <live-url>/sw.js | grep CACHE), read on-main horizon/plan docs. Treat memory, compaction summaries, and any spec as claims to verify — not a task list. A task is "open" only after you confirm it isn't already shipped on main.Before any commit and before any stochastic / AI-batch run, write the explicit pass/fail criterion AND the current green baseline. No proceeding on a partial win rationalized afterward. Detector-armed: prove RED on a known-bad input before trusting any test/detector to certify GREEN.
Every claim about what code/infra DOES ("covered", "inherits X", "verified", "handled by Y") cites a runnable/readable artifact — test path, command, or file:line. Reading the mechanism is not verifying it; run the real artifact. Once the cited artifact is green, do not re-litigate the prose around it.
Fix in order: RLS hole > crash/silent-failure > wrong clinical/data output > leak > cosmetic. Halt at the current phase (fix before advancing) on: RLS hole, crash, red tests, failed build, failed deploy. Never force-push over a broken deploy — rollback and investigate. Run the deploy-primitives §3 RLS sanity pass on ANY schema-adjacent change (shared Postgres across five repos); record the result line in IMPROVEMENTS.md even when clean.
Branch Codex/<slug> → PR → CI + the repo's wired reviewer → merge → verify-deploy. Never push direct to main.
Per repo: findings table (severity | file:line | issue) → fixed + self-merged (PR# + root cause + verify-deploy witness) → BLOCKED ON EIAS (carve-out PRs, one line each) → RLS result (or n/a) → anything left parked + its trigger. End with a consolidated IMPROVEMENTS.md.
Reinvent the pipeline/spec; paraphrase clinical skill content into code (verbatim port only); exceed maxAttempts>3 on extract/emit; auto-flip q.c / c_accept / curator overrides / distractor empty-slots; collapse multi-accept Qs; trust a search snippet over live state.