メニュー
Execute a Night Watch fix Mission - reproduce, fix, test, and open a PR for an incident dispatched by the watchman. Use when a mission briefing references a Night-Watch fingerprint.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/dapperdivers/roundtable-arsenal --skill night-watch-fixコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Synthesize domain knight summaries into a comprehensive Daily Briefing for Derek's Obsidian vault. Your output IS the briefing file — write the full document, not a summary of it.
Procedure for the morning-briefing verify_claims step: re-run the check behind every mechanically-verifiable claim in the domain summaries, build the authoritative knight-liveness map from vault file mtimes, update the open-items ledgers, and emit one JSON verification report that the synthesizer treats as the only source of numbers.
Protocol for the per-domain open-items ledger at /vault/Briefings/Ledger/<domain>.json. Replaces prose memory as the carry-forward mechanism for tracked items: Day-N counters are computed from first_seen, items are re-verified before being carried, and resolutions are recorded machine-readably so they can never be silently lost.
SOC 職業分類に基づく
SKILL.md を表示中
| name | night-watch-fix |
| description | Execute a Night Watch fix Mission - reproduce, fix, test, and open a PR for an incident dispatched by the watchman. Use when a mission briefing references a Night-Watch fingerprint. |
You received a Mission briefing with a fingerprint, evidence, and a target repo. The deliverable is a PR, or an explicit, well-argued "not a bug" verdict. Follow coding-agent rules (branch, tests, PR); this skill adds the Night Watch specifics.
Read your repo's codebase skill first: coding/roundtable-operator,
coding/pi-knight-runtime, coding/roundtable-ui, or coding/roundtable-arsenal.
| Repo | Verify before push |
|---|---|
| dapperdivers/pi-knight | npm ci && npx tsc --noEmit && npm test && npm run build |
| dapperdivers/roundtable-ui | cd api && go build ./... && go vet ./... && go test ./...; UI changes: cd ui && npm install && npm run build |
| dapperdivers/roundtable | go build ./... && go vet ./...; run make test (envtest) — if the sandbox can't, say so in the PR body |
| dapperdivers/roundtable-arsenal | skills are markdown: valid YAML frontmatter (name, description), check referenced paths/commands actually exist |
| dapperdivers/nats-bridge | check package.json/Makefile for the test command; at minimum build clean |
| dapperdivers/dapper-cluster | kubernetes/apps/roundtable/** paths ONLY — never touch anything else. Update the matching kustomization.yaml for new files. |
Reproduce first when feasible. A failing test that demonstrates the bug is worth more than the fix itself — it becomes the regression guard. If you cannot reproduce, say so in the PR body and explain your confidence anyway.
Branch: night-watch/<fingerprint>. Commits: conventional
(fix: <what> (night-watch <fp>)). Never push to main. No Co-Authored-By lines.
Smallest correct fix. No drive-by refactors; the human reviewing at 7 AM must be able to grasp the diff in one read.
PR body template (the trailer line is machine-read — keep it exact):
## Night Watch fix
**Incident:** <one-line summary>
**Evidence:** <key log lines / metrics from the briefing>
**Root cause:** <what was actually wrong>
**Fix:** <what you changed and why this addresses the root cause>
**Reproduced:** yes — <how> | no — <why not>
**Tests:** <suites run + results>
Night-Watch-Fingerprint: <fp>
Do NOT run gh pr merge in any form. Open the PR and stop.
(Tier rules will be enabled here in Phase 3 — tier 1: arsenal + roundtable
manifests may auto-merge on green; tier 3: operator Go code, workflows, RBAC,
renovate config NEVER auto-merge.)
.github/workflows/**kubernetes/apps/roundtable/infrastructure/app/*rbac*.yaml, *secret*.yaml.renovate/**, renovate.json*If the fix genuinely requires one of these, stop and say so in your result — that escalation is a human decision.
End your result with: PR URL, fingerprint, repos touched, test results. The watchman reads Mission results to update the ledger — make them parseable at a glance.