wiki-wasp-drone — Claude Code subagent: what it does, how to install
wiki-wasp-drone maps repository components into atomic wiki files, tracks ADRs from git commits, and catches contract contradictions.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install documentation-tools@wasp-nestWhat wiki-wasp-drone does
The subagent parses codebases to isolate thirteen entity categories, spanning functions, database tables, environment keys, and UI components. It relies on ts-morph when inspecting JavaScript and TypeScript files, while generating stub files for other programming languages. Every discovered item turns into an isolated markdown document with bidirectional wikilinks inside library/knowledge/private/wiki/.
It parses git history to identify architectural choices and files them as decision records. When a component signature changes, the agent applies an alert sequence across four artifacts: a stale marker on the prior file, a contradiction note on the current page, an entry in the daily report, and a response flag.
Code editing remains out of bounds: the drone treats the codebase as read-only. It also leaves root catalog files like index.md untouched, delegating their assembly to the companion TypeScript driver. Each documentation note is strictly capped at 300 lines to prevent bloated files.
What it helps with
- map code components into interconnected atomic markdown notes
- derive architectural decision records from git commit logs
- track breaking contract changes across project revisions
- validate wiki wikilinks and frontmatter structure in lint mode
Example prompts for the agent
- Run lint mode over the wiki documentation to spot broken links
- Extract entity pages for all handlers inside
src/routes/ - Generate decision records from recent commit messages
How to install wiki-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install documentation-tools@wasp-nest2Manually: put the files in place
.claude/agents/wiki-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/wiki-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/wiki-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about wiki-wasp-drone
How to install wiki-wasp-drone in Claude Code?
Add the repository registry via /plugin marketplace add legioncodeinc/vibe-coding-tools, then run /plugin install documentation-tools@wasp-nest. Alternatively, place .claude/agents/wiki-wasp-drone.md into your project.
What does wiki-wasp-drone do?
It maps codebases into structured markdown documentation, extracts architectural records from git logs, and warns about broken component contracts.
Does this subagent modify source code?
No, it reads source files without altering them. Its write access is restricted entirely to documentation files inside library/knowledge/private/wiki/.