From brewdoc
Generates documentation for Claude Code installations: internal overviews of local setups (CLAUDE.md, rules, agents, skills, memories), external docs on hooks/context/agents, or web research from forums/GitHub.
npx claudepluginhub kochetkov-ma/claude-brewcode --plugin brewdocThis skill is limited to using the following tools:
Generates documentation about your Claude Code installation and environment.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Generates documentation about your Claude Code installation and environment.
Detect mode from $ARGUMENTS:
$ARGUMENTS value | Mode | Sub-mode |
|---|---|---|
| empty | INTERNAL | — |
ext or external (alone) | EXTERNAL | default |
ext context or external context | EXTERNAL | context-schema |
starts with r or research | RESEARCH | query = rest of args |
After detection, load the appropriate reference file:
references/internal-mode.mdreferences/external-mode.mdreferences/research-mode.mdAll generated docs go to ~/.claude/brewdoc/ (global, not project-specific).
Create if not exists: mkdir -p ~/.claude/brewdoc
Append entry to ~/.claude/brewdoc/INDEX.jsonl:
{"ts":"2026-02-28T10:00:00","mode":"internal","path":"~/.claude/brewdoc/20260228_my-claude-internal.md","title":"Internal Claude Setup Overview","version":"1.0"}
If an existing entry for the same mode exists: use AskUserQuestion — header: "INDEX", question: "Entry for this mode already exists (v{VERSION}). Update it?", options: "Yes, update (bump version)" / "No, create new entry".
Goal: Document your local Claude Code setup — CLAUDE.md files, rules, agents, skills, memories.
Sources to analyze:
~/.claude/CLAUDE.md — global instructions~/.claude/rules/*.md — global rules~/.claude/agents/*.md — global agents~/.claude/skills/ — global skillsCLAUDE.md (current working directory).claude/rules/*.md — project rules~/.claude/projects/**/memory/MEMORY.md — memory filesProcess:
Explore agents, one per source group: (1) global ~/.claude config, (2) project .claude config, (3) memory files~/.claude/brewdoc/YYYYMMDD_my-claude-internal.mdreviewer agent to validate facts (file paths exist, content accurate)Output document structure:
# Claude Code Internal Setup — {date}
## Global Configuration
### Instructions (CLAUDE.md)
### Rules ({N} rules)
### Agents ({N} agents)
### Skills ({N} skills)
## Project Configuration
### Project Instructions
### Project Rules
## Memory
### Active Memories ({N} entries)
## Summary
| Component | Count | Location |
|-----------|-------|----------|
Goal: Document Claude Code's hook/context/agent architecture from official sources + local analysis.
Sub-mode default:
general-purpose agents for: official docs (code.claude.com), GitHub releases, community forums~/.claude/brewdoc/YYYYMMDD_my-claude-external.mdSub-mode context-schema:
~/.claude/brewdoc/external/YYYYMMDD_context-schema.mdGoal: Research a specific query about Claude Code using multiple sources.
Query: everything after r or research in $ARGUMENTS
Process:
general-purpose agents per source group in parallelreviewer agent to validate facts and source reliability~/.claude/brewdoc/YYYYMMDD_research-{slug}.mdOutput structure:
# Research: {query} — {date}
## Findings
### {Source Group 1}
...
## Sources
| Fact | Source | Reliability |
|------|--------|-------------|
## Review Verdict