Skip to content

bird-chinese-community/BIRD.skills / bird-agent

bird-agent

Verified

Write, review, discover, lint, format, and validate BIRD 2/3 routing-daemon projects with the @birdcc toolchain. Use for bird.conf, bird2.conf, bird3.conf, bird6.conf, .bird/.bird2/.bird3 files, bird.config.json, birdcc.config.json, include graphs, BIRD filters and protocols, birdcc init/lint/fmt/lsp, or bird -p checks. Treat BIRD 1 as legacy and verify it with the actual BIRD 1 binary. Route editor and CLI installation to birdcc-installer, GitHub Actions to birdcc-cicd, runtime incidents to bird-troubleshooting, and implementation archaeology to bird-source-explorer.

references/examples.md

View on GitHub
# BIRD Task Patterns

## Unknown project shape

1. Run `detect_bird_context.py`.
2. If discovery is ambiguous, run `birdcc init . --dry-run --json`.
3. Explain the selected candidate, ignored fragments, and confidence.
4. Offer to create `bird.config.json`; do not write it without approval.

## Cross-file diagnostic

1. Identify the configured `main` entry and include roots.
2. Run `birdcc lint <main> --json`; cross-file analysis is enabled by default.
3. Attribute each diagnostic to its actual URI rather than the entry file that imported it.
4. If limits are reached, raise `--include-max-depth` or `--include-max-files` only enough for the
   observed graph.

## Formatting request

1. Run `birdcc fmt <file> --check`.
2. Show the proposed change.
3. After explicit approval, run `--write`.
4. Re-run lint and native validation.

## BIRD 2 and BIRD 3 repository

1. Model independent routers with `workspaces` or pass each entry explicitly.
2. Use the matching BIRD 2 or BIRD 3 binary for each native parse check.
3. Treat the shared `bird2` editor filetype as a compatibility identifier, not a version
   selection mechanism.

## Legacy BIRD 1

1. Explain that the modern toolchain targets BIRD 2/3.
2. Use lint and formatting only as best-effort assistance.
3. Configure `bird.binaryPath` or `bird.validateCommand` for the real BIRD 1 binary.
4. Do not invent a `--target` or `--bird-version` CLI option.

## Unexpected runtime behavior

1. Confirm static lint and `bird -p` results.
2. Route operational symptoms to `bird-troubleshooting`.
3. Route implementation questions to `bird-source-explorer`.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall