bird-troubleshootinglisted

Diagnose active BIRD daemon incidents across config, runtime, environment, sockets, logs, source, and tooling. Use when BIRD fails to start or reload, crashes, loses sessions/routes, behaves differently after lint passes, or when birdcc and bird -p disagree. Collect read-only evidence first, protect routing secrets, and route isolated config edits to bird-agent or pure implementation research to bird-source-explorer.
bird-chinese-community/BIRD.skills · ★ 3 · Code & Development · score 72

Install: claude install-skill bird-chinese-community/BIRD.skills

# BIRD Troubleshooting Determine whether the failure is discovery, static analysis, native parsing, runtime state, environment, or an upstream implementation defect. ## Safety - Start read-only. Do not reload, reconfigure, restart, kill, or attach a debugger to production BIRD without explicit authorization. - Redact passwords, peer IPs, private ASNs, communities, socket paths, and policy details before sharing output. - Treat custom `validateCommand` values and workspace scripts as executable code. Show them before running in an untrusted checkout. - Preserve exact error text and timestamps, but do not dump whole production configs or logs. ## Workflow 1. Run: ```bash uv run scripts/collect_diagnostics.py --root . ``` Read [`references/troubleshooting-workflow.md`](references/troubleshooting-workflow.md) for interpretation. 2. Establish BIRD version/build, selected config entry, project config, binary paths, the exact failing command, and last known good state. 3. Reproduce at the narrowest read-only layer: - discovery → `birdcc init . --dry-run --json`; - static/cross-file → `birdcc lint <entry> --json`; - native parse → matching `bird -p -c <entry>`; - live state → user-approved read-only `birdc show ...` commands. 4. If lint fails, route the fix through `bird-agent`. If lint succeeds but native parse fails, compare binary version, includes, generated inputs, permissions, and environment. 5. If parsing succeeds but runtime beha