원클릭으로 Manus에서 모든 스킬 실행

toranot-ship

스타1

포크0

업데이트2026년 6월 9일 19:48

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.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

Eiasash

Eiasash/Toranot

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Toranot Ship Pipeline

Single-command production ship for github.com/Eiasash/Toranot → toranot.netlify.app.

This skill is user-invokable only — Codex will not auto-run it, because it pushes to production and touches a live PAT.

Preconditions (ask the user if unclear)

Working tree is in the Toranot repo root (usually /home/Codex/Toranot).
User has provided a fresh GitHub PAT for this session. Never store it. Paste into the $GH_PAT environment variable only.
There are real, staged or unstaged changes worth shipping (git status not clean).
User has edited the README.md Recent Changes section OR authorized this skill to add a terse one-liner.

If any precondition is unmet, stop and ask.

Pipeline (Strict Order)

Each step MUST pass before the next runs. On any failure: stop, surface the exact error, and do not proceed.

Step 1 — TypeScript gate

npx tsc --noEmit

Zero errors required. No suppressions.

Step 2 — Full vitest suite

npx vitest run --reporter=dot

All 2271 tests across 72 files must pass (last audited: 2026-05-01). If a new test was added, the new count is fine — but it must match the README/AGENTS.md claim (update both in the same commit if the number moves).

Step 3 — Production build + bundle gate

npx vite build

Then assert main bundle stays under 150KB:

bash .agents/skills/toranot-ship/scripts/preflight.sh --bundle-gate

(Falls back to du -sb dist/assets/index-*.js | awk '{ if ($1 > 153600) exit 1 }'.)

Step 4 — README touch-up

If the user did not update README.md Recent Changes, prompt for a one-line entry:

- YYYY-MM-DD: <short summary> (<short hash will go here>)

Commit it in the same commit as the feature.

Step 5 — Branch-push with PAT rotation + PR

Uses .agents/skills/toranot-ship/scripts/push-with-pat.sh. It NEVER pushes main directly — the release path is branch → PR → CI green + Codex review → merge (AGENTS.md):

Resolves the ship branch: reuses the current non-main branch, or creates codex/ship-<utc-stamp> when invoked from main. Refuses main outright.
git remote set-url origin https://$GH_PAT@github.com/Eiasash/Toranot.git
git config user.email "eias@toranot.app" + git config user.name "Eias"
git add -A && git commit -m "<type>: <description>" && git push -u origin <ship-branch>
Immediately git remote set-url origin https://github.com/Eiasash/Toranot.git (scrubs PAT)
Opens the PR via gh pr create (or prints the compare URL if gh is unavailable)
Print reminder: Revoke at https://github.com/settings/tokens

Commit message convention: feat:, fix:, refactor:, test:, chore:, docs:.

Step 6 — Netlify deploy verification (after the PR merges)

Uses .agents/skills/toranot-ship/scripts/verify-deploy.sh:

Poll https://api.netlify.com/api/v1/sites/85d12386-b960-4f65-bee8-80e210ecd683/deploys?per_page=1
Wait up to 5 minutes. State progression: uploading → building → ready.
On ready: assert commit_ref matches the just-pushed SHA.
On error: surface the build log URL, stop, do NOT mark success.

Step 7 — Post-deploy audit sweep

Delegate to the toranot-auditor subagent with a fresh context. It checks:

Dismissed tasks leaking into aggregations
RULES.length assertion still matches rules.ts
Banned patterns (transition-all, confirm(), mid-file imports, will-change on animate-card-in)
console.log leaks
Test count drift between README/AGENTS.md and actual vitest output
Bundle size still <150KB on the deployed build

If the auditor flags anything, surface it as a follow-up — do not auto-fix on the same ship.

Failure modes + recovery

Failure	Action
tsc errors	Stop. Surface errors. Do NOT skip.
vitest fails	Stop. Surface failing test names. Do NOT skip.
Bundle >150KB	Stop. Run `npx vite-bundle-visualizer` or check lazy() coverage.
Push rejected (non-fast-forward)	`git pull --rebase origin main`, resolve, retry. Never force-push `main`.
Netlify stuck `building` >5 min	Trigger retry via Netlify MCP, re-poll.
Netlify `error`	Fetch build logs, surface to user, do NOT declare success.
Auditor findings	Surface as a `toranot-followups.md` note. User decides whether to ship a follow-up.

Never do

Never git push --force to main.
Never leave the PAT in the git remote — always scrub immediately after push.
Never skip steps 1–3 to "just get it out".
Never edit sw.js CACHE_VERSION manually — Vite plugin stamps it.
Never merge changes that edited 1-of-5 room-format files without the other 4 (see hooks/room-format-drift.js).

이 저장소의 다른 Skills

같은 저장소

add-clinical-rule

Eiasash/Toranot

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

2026-06-091

source-command-audit-fix-deploy

Eiasash/Toranot

Full audit → fix → test → build → deploy → verify cycle for this repo. Auto-detects repo; captain-mode with verify-first + merge carve-outs.

2026-06-091

source-command-szmc-clinical-notes

Eiasash/Toranot

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.

2026-06-091

source-command-toranot-update-skill

Eiasash/Toranot

Auto-update SKILL.md (toranot-dev) with current ground truth. Run after every deploy or when skill feels stale.

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.

2026-04-181

name	toranot-ship
description	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.
disable-model-invocation	true

Toranot Ship Pipeline

Single-command production ship for github.com/Eiasash/Toranot → toranot.netlify.app.

This skill is user-invokable only — Codex will not auto-run it, because it pushes to production and touches a live PAT.

Preconditions (ask the user if unclear)

Working tree is in the Toranot repo root (usually /home/Codex/Toranot).
User has provided a fresh GitHub PAT for this session. Never store it. Paste into the $GH_PAT environment variable only.
There are real, staged or unstaged changes worth shipping (git status not clean).
User has edited the README.md Recent Changes section OR authorized this skill to add a terse one-liner.

If any precondition is unmet, stop and ask.

Pipeline (Strict Order)

Each step MUST pass before the next runs. On any failure: stop, surface the exact error, and do not proceed.

Step 1 — TypeScript gate

npx tsc --noEmit

Zero errors required. No suppressions.

Step 2 — Full vitest suite

npx vitest run --reporter=dot

Step 3 — Production build + bundle gate

npx vite build

Then assert main bundle stays under 150KB:

bash .agents/skills/toranot-ship/scripts/preflight.sh --bundle-gate

(Falls back to du -sb dist/assets/index-*.js | awk '{ if ($1 > 153600) exit 1 }'.)

Step 4 — README touch-up

If the user did not update README.md Recent Changes, prompt for a one-line entry:

- YYYY-MM-DD: <short summary> (<short hash will go here>)

Commit it in the same commit as the feature.

Step 5 — Branch-push with PAT rotation + PR

Uses .agents/skills/toranot-ship/scripts/push-with-pat.sh. It NEVER pushes main directly — the release path is branch → PR → CI green + Codex review → merge (AGENTS.md):

Resolves the ship branch: reuses the current non-main branch, or creates codex/ship-<utc-stamp> when invoked from main. Refuses main outright.
git remote set-url origin https://$GH_PAT@github.com/Eiasash/Toranot.git
git config user.email "eias@toranot.app" + git config user.name "Eias"
git add -A && git commit -m "<type>: <description>" && git push -u origin <ship-branch>
Immediately git remote set-url origin https://github.com/Eiasash/Toranot.git (scrubs PAT)
Opens the PR via gh pr create (or prints the compare URL if gh is unavailable)
Print reminder: Revoke at https://github.com/settings/tokens

Commit message convention: feat:, fix:, refactor:, test:, chore:, docs:.

Step 6 — Netlify deploy verification (after the PR merges)

Uses .agents/skills/toranot-ship/scripts/verify-deploy.sh:

Poll https://api.netlify.com/api/v1/sites/85d12386-b960-4f65-bee8-80e210ecd683/deploys?per_page=1
Wait up to 5 minutes. State progression: uploading → building → ready.
On ready: assert commit_ref matches the just-pushed SHA.
On error: surface the build log URL, stop, do NOT mark success.

Step 7 — Post-deploy audit sweep

Delegate to the toranot-auditor subagent with a fresh context. It checks:

Dismissed tasks leaking into aggregations
RULES.length assertion still matches rules.ts
Banned patterns (transition-all, confirm(), mid-file imports, will-change on animate-card-in)
console.log leaks
Test count drift between README/AGENTS.md and actual vitest output
Bundle size still <150KB on the deployed build

If the auditor flags anything, surface it as a follow-up — do not auto-fix on the same ship.

Failure modes + recovery

Failure	Action
tsc errors	Stop. Surface errors. Do NOT skip.
vitest fails	Stop. Surface failing test names. Do NOT skip.
Bundle >150KB	Stop. Run `npx vite-bundle-visualizer` or check lazy() coverage.
Push rejected (non-fast-forward)	`git pull --rebase origin main`, resolve, retry. Never force-push `main`.
Netlify stuck `building` >5 min	Trigger retry via Netlify MCP, re-poll.
Netlify `error`	Fetch build logs, surface to user, do NOT declare success.
Auditor findings	Surface as a `toranot-followups.md` note. User decides whether to ship a follow-up.

Never do

Never git push --force to main.
Never leave the PAT in the git remote — always scrub immediately after push.
Never skip steps 1–3 to "just get it out".
Never edit sw.js CACHE_VERSION manually — Vite plugin stamps it.
Never merge changes that edited 1-of-5 room-format files without the other 4 (see hooks/room-format-drift.js).