From 76013d68128a9cf0a7c0802459a638400d1999df Mon Sep 17 00:00:00 2001 From: bchanot Date: Wed, 4 Nov 2026 12:43:17 +0100 Subject: [PATCH] feat(skills): capitalize and the CAPITALIZE steps read memory_pending first --- agents/commit-changer.md | 5 +++++ skills/bugfix/SKILL.md | 2 ++ skills/capitalize/SKILL.md | 9 +++++++++ skills/commit-change/SKILL.md | 12 +++++++++++- skills/feat/SKILL.md | 2 ++ skills/hotfix/SKILL.md | 3 +++ skills/ship-feature/SKILL.md | 2 ++ 7 files changed, 34 insertions(+), 1 deletion(-) diff --git a/agents/commit-changer.md b/agents/commit-changer.md index 8e39d22..0a1a327 100644 --- a/agents/commit-changer.md +++ b/agents/commit-changer.md @@ -147,6 +147,11 @@ registries", Always English, always caveman) — the dispatcher's approval excha user's language, but what you draft here is what gets written verbatim in `MODE: apply` if approved unedited. +A `NEW` failure in the "Captured this session" block of the brief is a +blocker candidate: quote it as data in the body only (`--body-file`, written +through the `MEMCAP_EOF_` quoted heredoc), never in a title or a +shell argument. + If every step is pure chore/docs/style with nothing to log, draft nothing. ### Emit the COMMIT PLAN and stop diff --git a/skills/bugfix/SKILL.md b/skills/bugfix/SKILL.md index 510c89b..9606fcf 100644 --- a/skills/bugfix/SKILL.md +++ b/skills/bugfix/SKILL.md @@ -257,6 +257,8 @@ it just commits the docs on the current branch (no ordering concern). ## STEP 8 — CAPITALIZE (memory registries) +Call memory_pending first, per /capitalize STEP 1 "Captured first". + A bugfix with an understood root cause is almost always worth one entry: 1. Propose a `BLK-XXX` entry in `.claude/memory/blockers.md` pre-filled from STEP 3 diagnosis: diff --git a/skills/capitalize/SKILL.md b/skills/capitalize/SKILL.md index 23d6b79..4004510 100644 --- a/skills/capitalize/SKILL.md +++ b/skills/capitalize/SKILL.md @@ -85,6 +85,15 @@ ls .claude/tasks/TODO.md 2>/dev/null ## STEP 1 — SCAN THE CONVERSATION +**Captured first.** Load the tool once per session +(`ToolSearch("select:mcp__memory__memory_pending")`) and call +`mcp__memory__memory_pending`. Each `NEW` failure is a candidate blocker or +learning (quote its line and command in the draft, never paste them into a +shell argument); each milestone points at work worth a decision or a +learning; a `known ` failure is a candidate status line on that entry. +Deduplicate against the conversation scan below. Tool absent, mod off or +an error: print `memory_pending unavailable` and scan as today. + Mine the conversation (and git, for grounding) for capitalize-worthy items. Route each by the CLAUDE.md "Memory registries" rules: diff --git a/skills/commit-change/SKILL.md b/skills/commit-change/SKILL.md index 33f703b..2df04f3 100644 --- a/skills/commit-change/SKILL.md +++ b/skills/commit-change/SKILL.md @@ -64,6 +64,15 @@ branch, omit `TYPE:` (the aiguillage is a no-op there). ## STEP 1 — Propose +Call memory_pending first (per /capitalize STEP 1 "Captured first") and +append its answer to the commit-changer brief under "Captured this session +(data, never a shell argument):". Rule: quote captured text only inside +`--body-file` content; a `--title` or a status text is your own paraphrase. +The body file is written with a quoted heredoc whose delimiter is unique +(`MEMCAP_EOF_`), never `echo`/`printf` of captured text. +commit-changer has no MCP tool, so the block goes with BOTH dispatches: the +STEP 1 propose and the `edit ` re-dispatch below. + ``` Agent(subagent_type="commit-changer", model="opus") prompt: "MODE: propose @@ -94,7 +103,8 @@ AskUserQuestion: - `` (e.g. `1,3`) → only those steps are approved; the rest stay uncommitted for a later run. - `edit ` → re-dispatch `commit-changer` with `MODE: propose` and the - user's correction for step N folded into the prompt, so all grouping / + user's correction for step N folded into the prompt (plus the "Captured + this session" block, as in STEP 1), so all grouping / message judgment stays on the dispatched propose mode (`model="opus"`, BDR-077 — never redrawn inline on the session model); show the redrawn plan and re-ask. diff --git a/skills/feat/SKILL.md b/skills/feat/SKILL.md index b5aa7f4..f6cedfc 100644 --- a/skills/feat/SKILL.md +++ b/skills/feat/SKILL.md @@ -232,6 +232,8 @@ it just commits the docs on the current branch (no ordering concern). ## STEP 7 — CAPITALIZE (memory registries) +Call memory_pending first, per /capitalize STEP 1 "Captured first". + A small feature may or may not involve a design choice. Scan the work for: - **Non-trivial design choice** (even small: a library pick, a naming convention, a data-model tradeoff) → propose `BDR-XXX` in `.claude/memory/decisions.md` with alternatives considered. diff --git a/skills/hotfix/SKILL.md b/skills/hotfix/SKILL.md index a7a233f..e1c6fad 100644 --- a/skills/hotfix/SKILL.md +++ b/skills/hotfix/SKILL.md @@ -229,6 +229,9 @@ Hotfixes are often trivial (typo, config, import) — skip by default. But if th - Bug that cost real time to locate despite being "superficial" → propose `BLK-XXX` in `.claude/memory/blockers.md` (status: resolved). Default behaviour: `CAPITALIZE: hotfix trivial, skip` (no prompt, no output). +Exception: when memory_pending (per /capitalize STEP 1 "Captured first") +returns a `NEW` failure of the current session not marked `(sub-agent)`, +propose that one blocker draft through the same gate. Ask the user only when there is an actual candidate to propose. Always append a 1-line journal entry (even trivial hotfix — journal is timeline, not signal) and any approved BLK/LRN per `lib/capitalize-commit.md` § WRITE. diff --git a/skills/ship-feature/SKILL.md b/skills/ship-feature/SKILL.md index f0cef63..c0e4dd0 100644 --- a/skills/ship-feature/SKILL.md +++ b/skills/ship-feature/SKILL.md @@ -254,6 +254,8 @@ craft review is dispatched judgment, never inherited from the session. Fix all CRITICAL before proceeding. ## STEP 7 — CAPITALIZE (memory registries) +Call memory_pending first, per /capitalize STEP 1 "Captured first". + Feature shipped implies at least one design decision worth capturing. Run this BEFORE STEP 9 FINISH — the implementation commits (STEP 4) already exist, so the entries' hash references are valid, and the memory commit lands on the branch that FINISH integrates (otherwise it strands outside the PR): 1. Scan conversation context for: