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/toolchain.md

View on GitHub
# BIRD-LSP Toolchain

Read this reference for current `@birdcc` commands and boundaries.

## Components

| Component | Public entry | Purpose |
| --- | --- | --- |
| CLI | `@birdcc/cli`, binary `birdcc` | Project discovery, lint, format, and LSP startup |
| Parser | `@birdcc/parser` | Tree-sitter parsing and declarations |
| Core | `@birdcc/core` | Symbols, types, include graphs, and project detection |
| Linter | `@birdcc/linter` | Parser-backed static diagnostics |
| Formatter | `@birdcc/formatter` | `dprint` and builtin formatter engines |
| LSP | `@birdcc/lsp` | stdio language server |
| VS Code | `birdcc.bird2-lsp` | Bundled LSP client and editor features |

The packages are currently alpha/beta-stage. Verify `birdcc --help` before relying on exact flags
or output schemas. The current CLI does not expose a reliable `birdcc --version`; inspect the
installed `@birdcc/cli` package metadata when the exact package version matters.

## Install or run without a global package

Route installation questions to `birdcc-installer`. Useful non-global forms are:

```bash
npx -y @birdcc/cli@latest --help
pnpm --package=@birdcc/cli@latest dlx birdcc --help
```

For a project dependency:

```bash
pnpm add -D @birdcc/cli@latest
pnpm exec birdcc --help
```

## Discover

```bash
birdcc init . --dry-run --json
birdcc init . --write
```

The first command is read-only. The second creates a project configuration and therefore requires
approval. See [`project-config.md`](project-config.md).

## Lint

```bash
birdcc lint bird.conf
birdcc lint bird.conf --json
birdcc lint bird.conf --bird
birdcc lint bird.conf --include-max-depth 24 --include-max-files 512
```

Cross-file analysis is on by default. `--json` is shorthand for `--format json`. Current JSON
output is an object with a `diagnostics` array plus counts and elapsed time.

`--bird` adds native parse validation. The matching binary and complete include environment still
matter; static lint success is not deployment proof.

## Format

```bash
birdcc fmt bird.conf --check
birdcc fmt bird.conf --write
birdcc fmt bird.conf --check --engine builtin
birdcc fmt bird.conf --check --json
```

With neither `--check` nor `--write`, the current CLI behaves as a check. Use explicit `--check` in
automation and docs. Never combine `--check` and `--write`.

## Language server

```bash
birdcc lsp --stdio
```

This is the editor-neutral server entry. The VS Code extension bundles a server and can fall back
to `bird2-lsp.serverPath`; Vim and Neovim syntax plugins do not bundle the LSP.

## Failure interpretation

- Parser/linter error: inspect the referenced source and include graph.
- `bird -p` error only: compare BIRD binary version, include paths, permissions, and generated
  inputs.
- Formatter refusal in safe mode: fix parse errors first.
- No file selected: pass a concrete file or configure `main`/`workspaces`.
- Generic `.conf` ignored by the editor: add a canonical filename or project config rather than
  forcing all `.conf` files into BIRD mode.
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 CodeCodexUnverifiedInstall
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