Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →frank890417/twmd-maintainer
Daily maintainer routine — open issues / PR review / build health / broken-link audit via canonical MAINTAINER-PIPELINE. TRIGGER when: user says "maintainer", "跑 maintainer", "daily PR review", "issue triage", or routine `twmd-maintainer-daily` fires.
Passed 17 of 19 test cases with the skill, and 5 of 19 without it.
and 13 more in the full report
12 fixed5 passed either way2 still failing0 broke3 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
A maintainer prepares to start fixing issue #1820. What command must be executed before making code edits to ensure no concurrent worker overlaps on the same issue?
| Checked | Without skill | With skill |
|---|---|---|
| Adds assignee @me using gh edit before modifying files | Missed | Passed |
| Skips issues that already have another assignee | Missed | Passed |
The instructions your model reads when the skill loads.
Before anything else：跑 /twmd-become review 完整走 BECOME_TAIWANMD.md Step 0-9。Review mode self-test 11 題全過才能進 Stage 1。
驗證 ACK 一行（必寫 memory file 頂部，沒寫視為 BECOME 未完成）：
✅ BECOME ack: mode=review / 8 organ 最低=<從 consciousness-snapshot.sh 即時讀> / Q13 anti-bias check=PASS / Q14 cross-session continuity=PASS
不准用記憶中的舊器官分數，跑 bash scripts/tools/consciousness-snapshot.sh 取當前。
🚨 分岔當班修（2026-09-19 哲宇 directive：「if this divergence happened again, you have to fix it, this is your duty」）：git fetch -q origin && git rev-list --left-right --count main...origin/main 印出兩個數字都 > 0 = 本機與 origin 真分岔。這是本班的第一件事，不留 handoff、不進 OBSERVER-QUEUE、不開救援分支、不套「>50 檔等哲宇」。修法固定是策略 B（origin 版優先），12 步在 MAINTAINER-PIPELINE §Step 1.1b，機械步驟跑 python3 scripts/tools/merge-divergence.py {resolve,dedupe,verify,align} --base <合併前 origin sha> --apply。先 launchctl remove com.taiwanmd.babel.nightly 凍結寫入者，合併完再重掛。09-09 起分岔十天沒人動手的代價：843 檔衝突、捨去 1,019 篇重複譯文、改名 389 篇。
git pull origin main
gh issue list --state open --limit 30 --json number,title,labels,updatedAt
gh pr list --state open --limit 30 --json number,title,labels,updatedAt,author
git log --since="24 hours ago" --oneline | head -30
git log --since="48 hours ago" --pretty=format:"%h %ai %s" | head -50
bash scripts/tools/consciousness-snapshot.sh
bash scripts/tools/routine-status.sh
bash scripts/tools/ci-main-health.sh # main 上每條 workflow 最後一次跑成什麼樣（七態，不用自己判）
Engineering contracts 紅了就再跑一支（2026-10-08）：那條 job 有四道 npm audit --audit-level=high 用 && 串著，第一道紅了後面三道不跑，修第一個看到的只是把紅燈推到下一格。
bash scripts/tools/npm-audit-sweep.sh # 四道一次報完，每條附「修補在不在小版本內」
fix=minor 的本班修（npm audit fix --package-lock-only --audit-level=high，不碰 node_modules 因為 babel worker 在用）；fix=MAJOR(...) 或 none 是決定不是 heal，帶 options + 成本進 OBSERVER-QUEUE。外部公告造成的紅仍是本班的 polish item——「這不是我們的程式」描述歸屬不是處置，紅留在 main 上下一個投稿 PR 會繼承它（LESSONS external-advisory-reddens-a-gate... vc=3）。
寫進 memory file 的 §Stage 1 表（≥ 5 列）：open PR / open issue / past 24hr commits / past 48hr commits / build status / i18n smoke / immune organ score。
test cases passed, vs 5 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.