bird-chinese-community/BIRD.skills / bird-source-explorer
bird-source-explorer
VerifiedTrace BIRD routing-daemon behavior through the actual C source tree. Use for implementation questions, suspected upstream bugs, parser/keyword origins, filter instructions, protocol state machines, route attributes, birdc commands, stack traces, or BIRD 2 versus BIRD 3 source comparisons. Prefer a local checkout or exact upstream tag/commit and cite concrete files, functions, and revisions. Route config linting to bird-agent and active incidents to bird-troubleshooting.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.5 KB |
| agents/openai.yaml | config | 310 B |
| evals/evals.json | config | 1.5 KB |
| metadata.json | config | 456 B |
| plugin.json | config | 552 B |
| references/source-research.md | markdown | 2.3 KB |
references/source-research.md
View on GitHub# BIRD Source Research
## Establish revision
In a local checkout:
```bash
git status --short --branch
git rev-parse HEAD
git describe --tags --always
```
Do not cite uncommitted content as upstream behavior without saying the tree is dirty.
Official sources:
- GitLab: `https://gitlab.nic.cz/labs/bird`
- GitHub mirror: `https://github.com/CZ-NIC/bird`
Prefer immutable tag or commit links.
## Source map
| Area | Start here |
| --- | --- |
| Global config loading | `conf/conf.c`, `conf/cf-lex.l`, `conf/confbase.Y` |
| Filter language grammar/runtime | `filter/config.Y`, `filter/f-inst.c`, `filter/filter.h` |
| Route tables and attributes | `nest/rt-table.c`, `nest/route.h` |
| BGP config/runtime/attributes | `proto/bgp/config.Y`, `proto/bgp/bgp.c`, `proto/bgp/attrs.c`, `proto/bgp/packets.c` |
| OSPF | `proto/ospf/config.Y`, `proto/ospf/ospf.c`, `proto/ospf/rt.c` |
| CLI | `client/`, protocol-specific command hooks |
| OS integration | `sysdep/unix/`, `sysdep/linux/` |
| Tests | `test/` and protocol-local test fixtures |
Use `attrs.c`, not the obsolete/singular guess `attr.c`.
## Trace patterns
### Keyword or syntax
1. Search the lexer keyword table or `CF_KEYWORDS`.
2. Find grammar productions in `conf/*.Y`, `filter/config.Y`, or `proto/*/config.Y`.
3. Follow the semantic action into a config structure.
4. Find the commit/runtime hook that consumes it.
5. Find parser or integration tests.
### Filter method
1. Search the method name in `filter/config.Y`.
2. Identify the instruction/function in `filter/f-inst.c`.
3. Follow helpers and value types in `filter/filter.h` or `nest/route.h`.
4. Check error handling and mutation/copy semantics.
### Protocol behavior
1. Locate the protocol config and registration structure.
2. Trace state-machine callbacks and timers.
3. Follow packet encode/decode or route import/export hooks.
4. Check compile-time flags and version guards.
### Crash
1. Match the binary build and debug symbols.
2. Resolve the stack frame to an exact source revision.
3. Trace ownership, bounds, state, and error cleanup around the frame.
4. Search tests and later fixes without assuming correlation proves the cause.
## Answer format
State:
1. revision examined;
2. definition/registration path;
3. runtime path;
4. BIRD 2/3 differences;
5. tests or coverage gap;
6. confidence and remaining unknowns.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |