PLUGIN brewdoc

Brewdoc Overview

Brewdoc keeps documentation in sync with the codebase, documents your Claude Code setup, and exports documents to PDF or a shareable link. 5 skills, no agents, no registered hooks; docsync-setup installs optional hooks into your project on request.

Install

Install prompt- if Claude refuses, paste this into the chat

Execute these commands in this Claude Code session, one by one, show full output for each, do not skip any, do not summarize:

1. claude plugin marketplace add https://github.com/kochetkov-ma/claude-brewcode
2. claude plugin install brewdoc@claude-brewcode

After all commands succeed, run `/reload-plugins`. If `/reload-plugins` is unavailable, tell me to type `exit` and run `claude` again. Run the commands now.

What you get

SkillDoesLink
docsync-setupTracks doc staleness by frontmatter date through project hooksSkill
my-claudeDocuments your Claude Code installation, architecture or a research querySkill
memory-sync-setupGenerates a project-local /memory-sync skillSkill
md-to-pdfConverts Markdown to PDF with reportlab or weasyprintSkill
publishPublishes text, files or sites to brewpage.app, returns the URLSkill

Commands, arguments and models: Skills.

/brewdoc:docsync-setup sync           # Sync stale docs (with confirmation)
/brewdoc:md-to-pdf README.md          # Convert markdown to PDF
/brewdoc:publish "Hello world"        # Publish to brewpage.app, returns the URL

brewcode mods: Prompt placeholders · Plan-mode effort · Reminders · all mods

How it fits

Each skill is self-contained and independent of the others; the shared -setup convention gives the two setup skills one mode set. Brewdoc covers documentation utilities; Brewcode is the authoring toolkit: skills, agents, rules, semantic search, conventions and E2E tests. Both install from the same claude-brewcode marketplace.

Technical details

Naming and invocation rules #

A -setup suffix marks a skill that installs a mechanism you afterwards use instead of the skill: project-local hooks, or a generated /memory-sync command. Recurring tools keep bare names (md-to-pdf, publish, my-claude). Every -setup skill shares one mode set, in this order: status | install | upgrade | enable | disable | uninstall | purge; no argument means status when installed, install when not. Every brewdoc skill except /brewdoc:publish is user-invoked only (user-invocable: true + disable-model-invocation: true); publish is model-invocable, see the FAQ.

Install the whole suite (plugins and mods) #

The mods need Claude Code 2.1.301 or newer: run claude update, then restart Claude Code (type exit, then run claude).

Install prompt- if Claude refuses, paste this into the chat

First run `claude --version`. The mods need Claude Code 2.1.301 or newer. If it is lower, stop and tell me to run `claude update`, restart Claude Code (type `exit`, then run `claude`) and paste this prompt again.

Execute these commands in this Claude Code session, one by one, show full output for each, do not skip any, do not summarize:

1. claude plugin marketplace add https://github.com/kochetkov-ma/claude-brewcode
2. claude plugin install brewmod-placeholders@claude-brewcode
3. claude plugin install brewmod-plan-effort@claude-brewcode
4. claude plugin install brewmod-reminders@claude-brewcode
5. claude plugin install brewcode@claude-brewcode
6. claude plugin install brewdoc@claude-brewcode
7. claude plugin install brewtools@claude-brewcode
8. claude plugin install brewui@claude-brewcode

After all commands succeed, run `/reload-plugins`. If `/reload-plugins` is unavailable, tell me to type `exit` and run `claude` again. Run the commands now.
Plugin structure # 
brewdoc/
├── .claude-plugin/plugin.json   # manifest
├── hooks/hooks.json             # {"hooks":{}} -- no hooks registered
└── skills/                      # docsync-setup, my-claude, memory-sync-setup (references/), md-to-pdf, publish

docsync-setup installs project-local hooks into the target project, not into brewdoc. Skills use ${CLAUDE_SKILL_DIR} for their own files.

Safety and scope behaviour #

Docsync installation validates inputs before writing hooks, configuration and settings, merges settings under a lock with no backup file (the transaction is its own rollback), leaves an existing settings.json.bak and session state untouched, and on a write failure restores only files that still match this run’s writes. A generated memory-sync follows restrictions such as “only rules” or “do not touch agents”. Scope, depth and reach are separate choices. Claims are checked against current code, no file ends longer than it started, and a checker other than the writer verifies each batch.

Artifact metadata #

Every artifact a brewdoc -setup skill installs carries the shared provenance fields, resolved from the plugin’s .claude-plugin/plugin.json. Field table: Brewcode overview. /brewcode:setup-status reads them back and reports older installs as stale.

Skills

Commands, arguments and models for all 5 skills.

Installation

Install the suite from the marketplace.

Latest release

Download, changelog, and installation instructions.

GitHub source

Source code, README, and configuration files.

Update: /brewtools:plugin-update, /reload-plugins, then /brewcode:setup-status upgrade - FAQ