bird-source-explorerlisted

# BIRD Source Explorer Answer implementation-level questions about the BIRD routing daemon by exploring its C source tree. ## When to use this skill - The user asks how a BIRD feature, protocol, filter function, or attribute is implemented internally. - The user suspects a documented behavior does not match the code and wants source-level evidence. - The user wants to know which file or function defines a specific keyword, CLI command, or protocol message. - The user is debugging a crash or core dump and needs to map a stack trace to source locations. Do **not** use this skill for: - Editing, formatting, or linting a BIRD config (use `bird-agent`). - Installing BIRD tooling (use `birdcc-installer`). - General "what does this keyword do" questions that can be answered from the user guide (use `bird-agent` and its `query_bird_docs` MCP tool). ## Core principles 1. **Prefer the official source mirror.** Primary target is `https://github.com/CZ-NIC/bird`. Fall back to `https://gitlab.nic.cz/labs/bird` if the GitHub mirror is stale. 2. **Use deepwiki / Context7 for broad exploration.** For "where is X implemented" questions, start with deepwiki or Context7 over the BIRD repository to identify candidate files and functions. 3. **Use GitHub search / FetchURL for targeted evidence.** Once you know the likely file, fetch the raw source to quote the exact lines and explain the logic. 4. **Map findings to the user's version.** BIRD2 and BIRD3 share a l