w-docs — Claude Code skill: docs updates and installation
w-docs — a skill for Claude Code updates project docs after code or feature changes. It selects the docs layer that owns the change.
MIT 647 installs ★ 1 updated 2026-10-02
npx skills add blockmatic-icebox/basilic-skills --skill w-docs -a claude-codeWhat w-docs does
w-docs updates the project documentation layer responsible for a change. For architecture, commands, or workflows, it finds the relevant technical docs section and an existing topic page; it creates a page only when none fits. Canonical explanations go into MDX.
README changes are limited to updates about running, setup, or scripts. Agent rules change only when a constraint changes. The skill follows the repository’s documentation conventions and keeps MDX content out of READMEs and rules. It does not commit unless asked.
For file moves, it proposes a compact from/to list grouped by related files. It saves that list only when given a path, and moves files only when implementation is also requested.
What it helps with
- update technical docs after an architecture change
- add a new command to an existing MDX topic page
- sync the README with changes to setup or scripts
- revise an agent rule after a constraint changes
Example prompts for the agent
- Update the docs for this feature in the layer that owns it.
- Add this command to the existing MDX page and link it from the README.
- Propose a grouped from/to list for these files, but leave them in place.
How to install w-docs
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-docs -a claude-code2Manually: put the files in place
~/.claude/skills/w-docs/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/w-docs/
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-docs -a codex2Manually: put the files in place
.agents/skills/w-docs/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-docs -a cursor2Manually: put the files in place
.cursor/skills/w-docs/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install blockmatic-icebox/basilic-skills skills/workflow/w-docs2Manually: put the files in place
.github/skills/w-docs/SKILL.md1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-docs -a gemini-cli2Platform CLI
gemini skills install https://github.com/blockmatic-icebox/basilic-skills --path skills/workflow/w-docsManually: put the files in place
.devin/skills/w-docs/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-docs -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about w-docs
How do I install w-docs in Claude Code?
Run npx skills add blockmatic-icebox/basilic-skills --skill w-docs -a claude-code. The skill file is at ~/.claude/skills/w-docs/SKILL.md.
What does w-docs do?
It updates the docs layer responsible for a code or feature change: technical documentation, the README, or agent rules. It creates an MDX page only when no existing topic page fits.
When does w-docs edit the README or agent rules?
It edits the README for changes to setup, scripts, or how to run the app or package. It edits agent rules when a constraint the agent must follow changes.
Source text
SKILL.md · MIT
--- name: w-docs description: Document the current code or feature in the owning docs layer. disable-model-invocation: true --- Document the current code or feature. Follow the consuming repo's docs and README rules. Do not commit unless asked. Durable information architecture belongs in existing MDX; do not invent a second sitemap. Write to the layer that owns the change: | Layer | Role | Update when | | --- | --- | --- | | Technical docs (path in `AGENTS.md`) | Architecture, ADRs, how-to | Behavior, architecture, commands, conventions, or workflow changed | | Agent rules | Short constraints | A convention the agent must not violate changed | | Nearest README | How to run this app/package; links only | Scripts, setup, or package purpose changed | Inline comments only when the code is otherwise misleading. Do not copy MDX into rules or READMEs. Do not `@`-attach MDX. 1. Identify the matching docs section, then an existing topic page (create a page only if none fits). 2. Write or patch MDX if the canonical explanation changed. 3. Patch README only for run/setup/scripts; link the MDX. 4. Patch the glob-matched rule only if a constraint changed. 5. For mechanical file or doc moves: propose the smallest from/to list grouped by related files; drop folder-name prefixes inside groups. Save only if the user gave a path. Do not move files unless they also asked to implement.
© blockmatic-icebox · MIT · blockmatic-icebox/basilic-skills