bchanot/claude
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(ship-feature): doc-sync + doc-commit before FINISH — fixes docs stranded outside PR

Browse Source 
Reorder: DOC SYNC moves from STEP 9 (post-FINISH) to STEP 8 (pre-FINISH); FINISH → 9. doc-syncer PATCHES public docs but never commits them, and finishing-a-development-branch integrates only committed history — so on the push+PR path the patched docs were uncommitted and never reached the PR (twin of the capitalize PR-strand fix, BDR-034). STEP 8 now chains lib/doc-commit.md: surgical commit of the PATCHED_FILES, never git add -A, never .claude/ (rc 4 loud anomaly), no-op if nothing patched. Twin-chantier HTML comment removed — the twin is fixed, 'deferred' is now false.

Ref-coherence (part of the reorder — a swap flips meanings, it doesn't just drop a number): STEP 7 capitalize body refs 'STEP 8 FINISH' → 'STEP 9 FINISH' (lines 159, 189). README.md pipeline illustration completed — STEP 4-7 ends in capitalize (not 'finish'), STEP 8 = sync README, STEP 9 = finish; it had been silently wrong since e8eff7e moved DOC SYNC 8→9 without updating it, so completed rather than left accidentally-correct. Historical records (BDR-034, journal, CHANGELOG) left as-is — they said 'STEP 8' when it was true; append-only.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ho5EQCFTSvYamuRtVZpp2d
This commit is contained in:
Bastien Chanot 2026-06-27 02:07:14 +02:00
parent fb1f359da5
commit 636b49138c
2 changed files with 21 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@ -149,8 +149,9 @@ cd my-existing-project/
# → STEP 0: plugin check # → STEP 0: plugin check
# → STEP 1-2: brainstorm + plan (superpowers) # → STEP 1-2: brainstorm + plan (superpowers)
# → STEP 3: validation gate — user approval required # → STEP 3: validation gate — user approval required
# → STEP 4-7: implement (TDD) → review → finish # → STEP 4-7: implement (TDD) → review → capitalize (memory)
# → STEP 8: sync README # → STEP 8: sync README (doc-sync)
# → STEP 9: finish (merge / PR)
``` ```
For small features (1-5 files), use `/feat` instead — no orchestration overhead. For small features (1-5 files), use `/feat` instead — no orchestration overhead.

28
skills/ship-feature/SKILL.md
View File

@ -156,7 +156,7 @@ Load `$HOME/.claude/agents/analyzer.md`. Check: no regressions, no stale code, n
Invoke `superpowers:requesting-code-review`. Fix all CRITICAL before proceeding. Invoke `superpowers:requesting-code-review`. Fix all CRITICAL before proceeding.
## STEP 7 — CAPITALIZE (memory registries) ## STEP 7 — CAPITALIZE (memory registries)
Feature shipped implies at least one design decision worth capturing. Run this BEFORE STEP 8 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): 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: 1. Scan conversation context for:
- **Design / architecture choices with rationale** → candidate for `decisions.md` (BDR-XXX). - **Design / architecture choices with rationale** → candidate for `decisions.md` (BDR-XXX).
@ -186,20 +186,28 @@ If nothing substantive to log → print `CAPITALIZE: nothing substantive to log`
**Then commit the memory** — follow `$HOME/.claude/lib/capitalize-commit.md`: it **Then commit the memory** — follow `$HOME/.claude/lib/capitalize-commit.md`: it
surgically commits what capitalize just wrote (`.claude/memory` + `.claude/tasks` surgically commits what capitalize just wrote (`.claude/memory` + `.claude/tasks`
only, never `git add -A`) as one `chore(memory)` commit, reports the memory-commit only, never `git add -A`) as one `chore(memory)` commit, reports the memory-commit
hash, and no-ops if nothing was written. It runs BEFORE STEP 8 FINISH so the hash, and no-ops if nothing was written. It runs BEFORE STEP 9 FINISH so the
memory is integrated with the branch, not stranded outside the PR. memory is integrated with the branch, not stranded outside the PR.
## STEP 8 — FINISH ## STEP 8 — DOC SYNC
Invoke `superpowers:finishing-a-development-branch`. Tests pass, build clean, ready to merge. Run BEFORE STEP 9 FINISH. doc-syncer PATCHES public docs but does NOT commit them, and
`finishing-a-development-branch` integrates only COMMITTED history — so a patch left
uncommitted (or committed after) never reaches the merge/PR. Same PR-stranding class as the
STEP 7 capitalize fix (BDR-034).
## STEP 9 — DOC SYNC Load `$HOME/.claude/agents/doc-syncer.md`. Execute in automatic mode:
<!-- Stays post-FINISH = TWIN CHANTIER: doc-sync has the same PR-stranding bug
capitalize just fixed (artifacts written after integration). Deferred to
v-next; move it before FINISH then. Not fixed here to keep v1 scoped. -->
Load `$HOME/.claude/agents/doc-syncer.md`.
Execute in automatic mode:
`auto-mode scope: <list of files modified during this session>` `auto-mode scope: <list of files modified during this session>`
**Then commit the docs** — follow `$HOME/.claude/lib/doc-commit.md`: it surgically commits
ONLY the files doc-syncer patched (its `PATCHED_FILES` output, one path per line → one argv
arg each), never `git add -A`, never `.claude/`/`CLAUDE.md`, and no-ops if nothing was
patched. Report per its rc table — rc 4 = a LOUD upstream BDR-022 anomaly (doc-syncer
surfaced a forbidden path), not a silent skip. It runs BEFORE FINISH so the doc commit lands
on the branch FINISH integrates.
## STEP 9 — FINISH
Invoke `superpowers:finishing-a-development-branch`. Tests pass, build clean, ready to merge.
--- ---
## RULES ## RULES