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

chore(config): superpowers citers by bare name, routing map, docs, settings

Browse Source 
Every superpowers-prefixed skill call in ship-feature, init-project, tour,
deploy, audit-delta, plugin-advisor and lib/analyze-before-plan now names
the vendored skill directly. finishing-a-development-branch is described
as the upstream skill this config does not vendor (gitflow finish is the
integration path). CLAUDE.global.md Skill routing maps the four
non-vendored skills the vendored text still references. settings.json
loses the plugin key and its marketplace block; README, USAGE,
plugin-advisor and the profile skill describe superpowers as vendored
skills, always on, zero plugin cost. CHANGELOG entry with a known
residual.
This commit is contained in:
bastien
2026-09-28 14:54:53 +02:00
parent 18f8c898f8
commit ddea411491
16 changed files with 121 additions and 77 deletions
Download Patch File Download Diff File Expand all files Collapse all files
lib/analyze-before-plan.md
+4 -3
View File
@@ -103,9 +103,10 @@ backfill, if ever wanted, is `/prune-memory` passe D — never this snippet.
## ORDERING (orchestrators only)
`superpowers:brainstorming` / `writing-plans` are external skills — we cannot make them
read our registries. So this runs BEFORE them, pre-loading the disposition into the plan
they form. Mirror of capitalize-commit running BEFORE finishing-a-development-branch: there
`brainstorming` / `writing-plans` (vendored superpowers skills) are external skills — we
cannot make them read our registries. So this runs BEFORE them, pre-loading the
disposition into the plan they form. Mirror of capitalize-commit running BEFORE
`gitflow finish` (the upstream finishing-a-development-branch is not vendored): there
the memory commit must precede integration; here the memory read must precede planning.
## NO-OP / IDEMPOTENT
lib/capitalize-commit.md
+10 -8
View File
@@ -17,9 +17,10 @@ code already committed.
- Inline-commit flows (feat / hotfix / bugfix / commit-change): run it right
after writing the entries, on the current branch.
- Orchestrators that integrate via `superpowers:finishing-a-development-branch`
(ship-feature / init-project): run it BEFORE the FINISH step — otherwise the
memory commit strands outside the merge/PR. See ORDERING.
- Orchestrators that integrate via `gitflow finish` (the upstream
finishing-a-development-branch is not vendored; ship-feature / init-project):
run it BEFORE the FINISH step — otherwise the memory commit strands outside
the merge/PR. See ORDERING.
This snippet commits whatever is PENDING under `.claude/memory` + `.claude/tasks`;
it does NOT decide content. A flow whose gate wrote only a journal line yields a
@@ -65,11 +66,12 @@ no-match pathspec is filtered, not fatal).
## ORDERING (orchestrators only)
`finishing-a-development-branch` may merge-and-delete the branch or push a PR. A
memory commit created AFTER it lands outside the integrated history — stranded
on the PR path. So in ship-feature / init-project this snippet runs BEFORE
FINISH. The code commits already exist (implementation step), so the entries'
hash references are valid at this point.
`finishing-a-development-branch` (upstream superpowers skill, not vendored
here; `gitflow finish` is the only integration path) may merge-and-delete the
branch or push a PR. A memory commit created AFTER it lands outside the
integrated history — stranded on the PR path. So in ship-feature / init-project
this snippet runs BEFORE FINISH. The code commits already exist (implementation
step), so the entries' hash references are valid at this point.
## WHAT THIS DOES NOT DO
lib/doc-commit.md
+5 -4
View File
@@ -81,10 +81,11 @@ do NOT bypass them:
## ORDERING (orchestrators)
`finishing-a-development-branch` merges/pushes COMMITTED history only — it never commits
working-tree changes. A doc patch left uncommitted (or committed AFTER it) never reaches
the merge/PR. So this snippet runs BEFORE FINISH: the doc commit lands on the branch FINISH
integrates. Consumption is MECHANICAL (LRN-057 case a, like the memory commit) — production
`finishing-a-development-branch` (upstream superpowers skill, not vendored here;
`gitflow finish` is the only integration path) merges/pushes COMMITTED history only — it
never commits working-tree changes. A doc patch left uncommitted (or committed AFTER it)
never reaches the merge/PR. So this snippet runs BEFORE FINISH: the doc commit lands on
the branch FINISH integrates. Consumption is MECHANICAL (LRN-057 case a, like the memory commit) — production
on the branch = consumption by the merge, automatic.
## ACKNOWLEDGMENTS (conscious, not glossed)