Skip to content

docs(docs): add the VS Code install example and strip history from the standalone docs - #11

Merged
LittleCoinCoin merged 2 commits into
mainfrom
claude/readme-consistency-vscode-ea20c0
Sep 14, 2026
Merged

LittleCoinCoin merged 2 commits into
mainfrom
claude/readme-consistency-vscode-ea20c0

Conversation

@LittleCoinCoin

Copy link
Copy Markdown
Member

Why

The Agent Plugins 1.0 install path is now verified in VS Code: Command Palette, Chat: Install Plugin from Source, enter CrackingShells/colgrep-mcp. The README gives that walkthrough as the example instead of a hedge about the spec leaving installation to clients.

The standalone docs must read as-is. A README reader or a maintainer loading a dev skill has no access to the sessions that produced the rules, so history, development state and chat context are stripped from every authored document except CHANGELOG.md, __reports__/ and __roadmap__/, which are records by nature.

What changed

  • README.md: VS Code example under the Agent Plugins section; the Codex "not yet exercised end to end" caveat, the report pointers in Hooks and Development, and the "latest run" sentence are gone.
  • dev/skills/*: every MEM ("lead memory") and "lead memory" citation removed, along with PR numbers, incident dates, per-cycle anecdotes and this machine's paths. The rules they backed stay, cited to their reports.
  • AGENTS.md: the legend now defines KT-B/C/D/H, OBS-C/D/H, PH, CI and RI, so every id the skills cite resolves inside the repository (107 of 130 lines).
  • Three cross-references to headings that no longer exist (CONTRIBUTING.md#allowed-types, §Branching, AGENTS.md §Conventions/§Traps) are repointed.
  • drift-tests.md gains rows for test_packaging.py and test_hooks.py.

Gates

  • uv run pytest: 306 passed, 1 skipped
  • claude plugin validate . and ./dev: both pass
  • cz check --rev-range main..HEAD: successful

🤖 Generated with Claude Code

LittleCoinCoin and others added 2 commits September 14, 2026 15:40
…e standalone docs

The Agent Plugins 1.0 install path is verified in VS Code (Command Palette,
"Chat: Install Plugin from Source", the repository slug), so the README now
gives that walkthrough instead of a hedge about the spec leaving installation
to clients.

The standalone docs must read as-is: a README reader or a maintainer loading
a dev skill has no access to the sessions that produced the rules. The dev
skills cited MEM (the lead's memory), PR numbers, incident dates and this
machine's paths; those are removed, the rules they backed stay, and every
report shorthand the skills cite (KT-*, OBS-*, PH, CI, RI) is now a row of the
AGENTS.md legend so each citation resolves inside the repository. Three
cross-references to headings that no longer exist are repointed.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…elopment cycle

Nothing in the repository claimed LightOn's endorsement, but nothing denied it
either; a reader deciding where to file a colgrep bug needs the boundary stated
at the top. The new section tells a human reader who does the work here and how
a change reaches main, so the agent-run cycle is visible rather than implied by
the commit history, and names the two conditions it depends on: a frontier model
and a maintainer who reads every diff.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@LittleCoinCoin
LittleCoinCoin merged commit 4d20212 into main Sep 14, 2026
5 checks passed
@LittleCoinCoin
LittleCoinCoin deleted the claude/readme-consistency-vscode-ea20c0 branch September 14, 2026 14:17
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