From 8bff3350731e4f232d294d10d3e49a57440e7880 Mon Sep 17 00:00:00 2001 From: Bryan Fawcett Date: Tue, 6 Oct 2026 15:53:29 +0800 Subject: [PATCH 1/2] docs: load the Mzizi dev skills; progress reports and the merge gate Adds the canonical rule block from nyuchi/.github#87 after "Track big work in GitHub issues": load the Mzizi dev skills (digital-hygiene and progress-report), the 10-minute progress-report loop whose ticks never publish, release, merge or deploy without the owner's approval, and the merge gate. Refs nyuchi/.github#87 Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01GHjaH1Vt2dVLWU68iz8tFq --- AGENTS.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 4c54db0..9debe5f 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -41,3 +41,11 @@ Any substantial build, migration, investigation or multi-step task gets a GitHub - Post progress, decisions and a hand-off note (what's done, what's left, branch names) as issue comments — at each merge and before a session or agent finishes. - Work spanning repos gets a tracking issue that links the per-repo issues. - Never put secrets, credential status or exploitable detail in issues on public repos. + +## Dev skills, progress reports and the merge gate + +Load the Mzizi **dev skills** before starting work: `mzizi_get_skills category=dev` on the Mzizi MCP (`mcp.mzizi.dev`), or `@nyuchi/mzizi-skills` from npm. They are `digital-hygiene` and `progress-report`. + +- **Digital hygiene.** Check free disk before starting, clone only under `$TMPDIR`, share build caches, and audit, then delete, your clones once the work merges (`digital-hygiene` skill). +- **Progress reports.** All dev work runs on a 10-minute progress-report loop (`progress-report` skill): measured bars, what changed, and a final "Needs you:" line. Report ticks never publish, release, merge or deploy without the owner's approval. +- **Merge gate.** Merge only when the work is complete, CI is green, it's verified at runtime, and `/code-review` has run with findings resolved. From d1e47fd48e67777b4d52c011d4373d9f85048be7 Mon Sep 17 00:00:00 2001 From: Bryan Fawcett Date: Tue, 6 Oct 2026 16:49:59 +0800 Subject: [PATCH 2/2] docs: the clone-isolation rule joins the dev-skills block Clone only into a directory unique to you; never touch another agent's. Refs nyuchi/.github#87 Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01GHjaH1Vt2dVLWU68iz8tFq --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index 9debe5f..0bf5a69 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -47,5 +47,6 @@ Any substantial build, migration, investigation or multi-step task gets a GitHub Load the Mzizi **dev skills** before starting work: `mzizi_get_skills category=dev` on the Mzizi MCP (`mcp.mzizi.dev`), or `@nyuchi/mzizi-skills` from npm. They are `digital-hygiene` and `progress-report`. - **Digital hygiene.** Check free disk before starting, clone only under `$TMPDIR`, share build caches, and audit, then delete, your clones once the work merges (`digital-hygiene` skill). +- **Clone isolation.** Clone only into a directory unique to you; never touch another agent's. - **Progress reports.** All dev work runs on a 10-minute progress-report loop (`progress-report` skill): measured bars, what changed, and a final "Needs you:" line. Report ticks never publish, release, merge or deploy without the owner's approval. - **Merge gate.** Merge only when the work is complete, CI is green, it's verified at runtime, and `/code-review` has run with findings resolved.