extract-docslisted
Install: claude install-skill tamalCodes/birdsEye
# Extract docs
> **Dormant as of the zero-token rewrite.** birdsEye's `/birdseye:map` no
> longer invokes this skill - the map is now a pure local AST parse (graphify)
> with no model calls. This file is kept for a future opt-in `--with-llm` mode.
This is the half of `birdsEye` that answers the question the whole tool exists
for: *"I need to fix a bug in the auth module - which spec files should I read
first?"* The import graph says what auth is wired to. You say what has been
written down about it.
Write `birdseye/.cache/docs.json` and nothing else. Never modify the user's
source tree, and never write documentation into it.
## Non-negotiables
- **Only attach a doc to code you verified exists on disk.** A `documents` edge
to a path that is not there is worse than no edge.
- **Location is a hint, not the answer.** A doc sitting at the repo root can
still be about one module. Its title and first paragraph will usually say so.
This judgement is the reason a script is not doing this job.
- **Guardrails are quoted, not summarised.** Copy the bullet verbatim into
`guardrails`. The plain-English gloss goes in a *separate* field
(`guardrailsPlain`) and may not add any fact the bullet does not already
carry - it only unpacks jargon and shorthand.
- **One README and nothing else is a valid result.** Emit it and stop.
## Step 1 - find the docs
Use the `docGlobs` list from `birdseye.config.json` if it is there; otherwise
these defaults:
```
**/MAP.md **/AGENTS.md