Skip to content

docs: complete README skill lists — 34 → 36 skills, both blocks aligned (v0.16.2.1)#953

Open
ignsm wants to merge 3 commits intogarrytan:mainfrom
ignsm:docs/complete-readme-skill-lists
Open

docs: complete README skill lists — 34 → 36 skills, both blocks aligned (v0.16.2.1)#953
ignsm wants to merge 3 commits intogarrytan:mainfrom
ignsm:docs/complete-readme-skill-lists

Conversation

@ignsm
Copy link
Copy Markdown

@ignsm ignsm commented Apr 10, 2026

Summary

Pure documentation fix. Brings the README's skill lists and skill table in line with what ./setup actually installs into ~/.claude/skills/. Zero code changes, zero runtime effect.

The README has two skill-list strings users paste into their CLAUDE.md when they set up gstack in a new project:

  1. Install command block (line 49) — the blurb Claude Code is supposed to insert into CLAUDE.md during fresh install.
  2. "## gstack" CLAUDE.md example block (line 396) — the copy-paste example in the troubleshooting section.

Over time these drifted apart, AND both had fallen behind the actual ./setup output. Before this PR:

  • Install block (34 skills): had /connect-chrome, /plan-devex-review, /devex-review. Missing /pair-agent, /health, /checkpoint.
  • CLAUDE.md example (32 skills): had /open-gstack-browser, /pair-agent. Missing /plan-devex-review, /devex-review, /health, /checkpoint.

After this PR both blocks list the same 36 skills in the same order, matching what ./setup registers on a clean install.

On top of that, /health and /checkpoint also get two new rows in the big sprint skill table — both have been working skills for a while (health/SKILL.md, checkpoint/SKILL.md), but the README didn't mention them anywhere, so new users had no way to discover them.

Bisection

Three clean commits, each independently revertable:

  1. 6ef5696bdocs: complete and align README skill lists (36 skills, both blocks identical)

    • Adds /pair-agent to the install block.
    • Adds /plan-devex-review, /devex-review to the CLAUDE.md example block.
    • Replaces legacy /connect-chrome with canonical /open-gstack-browser.
    • Adds /health and /checkpoint to both blocks.
    • Verified via extracted-list diff: both blocks produce identical sorted sets.
  2. 63753d3fdocs: add /health and /checkpoint rows to README skill table

    • Two new rows in the big sprint skill table. /health after /benchmark (both measurement tools). /checkpoint after /learn (both session/state tools).
    • Specialist roles chosen to avoid adjacency collisions: /health → "Quality Engineer" (next to "Performance Engineer" for /benchmark), /checkpoint → "Session Bookmark" (avoids collision with /learn's "Memory").
  3. 4d11ef72chore: bump version and changelog (v0.16.2.1) (VERSION + CHANGELOG.md)

What's NOT in this PR

The Node server bundle build fix is deliberately out of scope. That fix is already in flight:

Either approach fixes the ./setup build error. I didn't want to triple-post the fix, so this PR stays README-only.

Voice calibration

Both new skill table entries match the existing table voice:

  • Lead with what the user can DO, not implementation details.
  • Include the concrete trigger phrase in quotes so readers know how to activate.
  • Avoid AI vocabulary (no "leverage", "robust", "comprehensive").
  • Pick a specialist role that doesn't collide with adjacent table entries.

/healthQuality Engineer — "Wraps your project's type checker, linter, test runner, dead code detector, and shell linter into one weighted 0-10 composite score. Tracks trends over time so you see whether the codebase is improving or rotting. Say 'how healthy is the codebase' and you get one number plus a per-tool breakdown."

/checkpointSession Bookmark — "Save and resume working state mid-sprint. Captures git state, decisions made, and what's left to do so you can pick up exactly where you left off, even across Conductor workspace handoffs or after a long break. Say 'where was I' or 'pick up where I left off' and it reads the latest checkpoint."

Test plan

  • grep "^## \[" CHANGELOG.md shows contiguous version sequence (0.16.2.1, 0.16.2.0, 0.16.1.0, 0.16.0.0, 0.15.16.0, 0.15.15.1, ...)
  • Both README skill-list blocks contain the same 36 skills in the same order (verified via extracted-list diff: install block line 49 and CLAUDE.md example block lines 396-401 produce identical sorted sets)
  • All 5 added skills appear in both blocks: /pair-agent, /plan-devex-review, /devex-review, /health, /checkpoint
  • Legacy /connect-chrome removed from the install block (still exists as a symlink alias at checkpoint-chrome → open-gstack-browser so existing installs keep working)
  • Big skill table has new rows for /health (after /benchmark) and /checkpoint (after /learn)
  • Both new skills resolve to real SKILL.md files on disk: checkpoint/SKILL.md, health/SKILL.md
  • Both new skills get linked by ./setup into ~/.claude/skills/checkpoint/SKILL.md and ~/.claude/skills/health/SKILL.md (verified on the upgrade session that surfaced this gap)

🤖 Generated with Claude Code

ignsm and others added 3 commits April 10, 2026 17:22
…dentical)

The README has two skill-list strings that users paste into their
CLAUDE.md when setting up gstack: the install command block (line 49)
and the "## gstack" CLAUDE.md example block (line 396). Over time
these drifted apart AND both fell behind what ./setup actually
registers into ~/.claude/skills/.

Before this commit:

  Install block (34): had /connect-chrome, /plan-devex-review,
    /devex-review. Missing /pair-agent, /health, /checkpoint.
  CLAUDE.md example (32): had /open-gstack-browser, /pair-agent.
    Missing /plan-devex-review, /devex-review, /health, /checkpoint.

After this commit, both blocks list the same 36 skills in the same
order. Changes:

1. Added /pair-agent to the install block (was only in the example).
2. Added /plan-devex-review and /devex-review to the example block
   (were only in the install block).
3. Replaced the legacy /connect-chrome reference with the canonical
   /open-gstack-browser. /connect-chrome still works as a symlink
   alias, but the README should advertise the current name.
4. Added /health and /checkpoint to both blocks. Both have been
   working skills for a while (health/SKILL.md, checkpoint/SKILL.md),
   get registered by ./setup on every install, and show up in
   ~/.claude/skills/ as live slash commands — but they were missing
   from the README everywhere, so new users had no way to discover
   them.

Placement: /health right after /benchmark (both measurement tools),
/checkpoint right after /learn (both session/state persistence),
matching the existing workflow-order grouping in the list.

Verified via extracted-list diff: both blocks now produce identical
sorted sets of 36 skill names.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Now that both skill-list blocks mention /health and /checkpoint, the
big sprint skill table needs matching rows so new users understand
what each skill does. Without table rows, a name in the list is just
a label without a description — users wouldn't know when to reach
for either skill.

Placement matches the list ordering from the prior commit:

- /health slots right after /benchmark (both are measurement tools
  that produce a score for the codebase).
- /checkpoint slots right after /learn (both are session/state
  persistence tools — /learn for cross-session learnings,
  /checkpoint for within-project resume state).

Specialist roles:

- /health is "Quality Engineer". Sits alongside "Performance
  Engineer" for /benchmark and "Staff Engineer" for /review.
- /checkpoint is "Session Bookmark". Deliberately avoids the
  "Memory" label since /learn (directly above it in the table) is
  already "Memory". Both are memory-adjacent but at different
  timescales: /learn remembers patterns across projects,
  /checkpoint remembers where you left off in one project.

Voice matches the existing table: one-line specialist role, two or
three sentences on what the user can DO, and the concrete trigger
phrase in quotes so readers know how to activate the skill.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant