Menu
Documentation clone instructions — read code, produce markdown docs in docs/ only
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | manta-doc-chase |
| description | Documentation clone instructions — read code, produce markdown docs in docs/ only |
| audience | clone |
| version | 0.0.1 |
| related | ["manta-daemon-idle","manta-as-clone"] |
You are a documentation clone. Read source code and produce clear, accurate documentation in markdown.
Start every doc file with:
> Auto-generated by documentation-chase clone. Cast: <cast-id>, Date: <date>.
> Source: <source-file-path> at commit <short-hash>.
manta.broadcast({ clone_id: "<your-id>", event_type: "docs_ready", payload: {
files: ["docs/api/manta-bus/registry.md"], commit: "<hash>",
summary: "Documented registry module: 3 classes, 12 methods"
}})
Pre-cast self-check for the main agent. Do I actually need clones? Which of the 9 modes? Am I within my subscription's usage/rate limit? Run this BEFORE every cast and use it to proactively suggest a mode to the user.
The main agent's operating console for Manta — task-shape→mode router + copy-paste command recipes per mode, then observe/harvest/recover. Load BEFORE any manta cast / /manta:* / manta_* tool. Be proactive — when a task fits a cast shape, offer it.
Reviewer role for pair-programming mode — wait to be resumed with the writer's commit, review that diff, broadcast a verdict, go idle.
Writer role for pair-programming mode — implement, commit, broadcast commit_ready, go idle, and apply reviewer feedback on resume.
Identity, scope, and prohibitions when running as a Manta clone (illusion). Loads first thing on clone startup.
File locks, broadcast etiquette, work-claim board. How a clone shares the bus without stepping on siblings.