Skip to content

bird-chinese-community/BIRD.skills / birdcc-installer

birdcc-installer

Verified

Install or migrate BIRD 2/3 editor support and @birdcc/cli. Use for the BIRD2 LSP VS Code extension, the separate TextMate syntax extension or extension pack, VS Code forks, BIRD.nvim, BIRD.vim, manual Neovim LSP wiring, JetBrains TextMate bundles, birdcc CLI installation, offline VSIX setup, or migrations from BIRD2.nvim/BIRD2.vim. Route config diagnostics to bird-agent and GitHub Actions to birdcc-cicd.

FileKindSize
SKILL.mdskill md3.5 KB
agents/openai.yamlconfig585 B
assets/logo-small.pngbinary2.9 KB
assets/logo.pngbinary6.5 KB
evals/evals.jsonconfig4.2 KB
metadata.jsonconfig817 B
plugin.jsonconfig509 B
references/cli.mdmarkdown1.6 KB
references/editors.mdmarkdown4.8 KB
references/offline.mdmarkdown1.5 KB
scripts/check_cli.pyscript2.3 KB
scripts/detect_editor.pyscript5.3 KB
scripts/detect_ide.pyscript18.3 KB

references/editors.md

View on GitHub
# Editor Installation

## Capability map

| Target | Highlighting | Diagnostics/navigation/formatting | Verified distribution |
| --- | --- | --- | --- |
| VS Code-like editors | `birdcc.vscode-bird2-conf` | `birdcc.bird2-lsp` | Marketplace/OpenVSX or VSIX |
| Neovim 0.9+ | `BIRD.nvim` | manual `birdcc lsp --stdio` wiring | Git repository/release |
| Vim 8+ | `BIRD.vim` | use `birdcc` commands externally | Git repository/release |
| JetBrains | imported TextMate bundle | use `birdcc` commands externally | VSIX content import |

The shared language/filetype ID is still `bird2`, including for BIRD 3 files.

## VS Code

For the complete experience, install the extension pack when it is available in the configured
registry:

```bash
code --install-extension birdcc.bird2-extension-pack
```

The equivalent explicit installation is:

```bash
code --install-extension birdcc.bird2-lsp
code --install-extension birdcc.vscode-bird2-conf
```

- Pack: https://marketplace.visualstudio.com/items?itemName=BIRDCC.bird2-extension-pack
- LSP: https://marketplace.visualstudio.com/items?itemName=birdcc.bird2-lsp
- Syntax: https://marketplace.visualstudio.com/items?itemName=BIRDCC.vscode-bird2-conf

The LSP extension provides diagnostics, completion, hover, symbols, navigation, formatting, and
optional native `bird -p` validation. The syntax extension is deliberately separate and provides
TextMate highlighting.

The LSP extension broadly recognizes `.conf` for compatibility but gates expensive BIRD features
behind canonical filenames, parsed BIRD declarations, or `bird.config.json.main`. Do not force
unrelated `.conf` files into BIRD mode.

## VS Code forks

Use the product's own extension panel and configured gallery. VSCodium and OpenVSX-backed products
can use:

```bash
codium --install-extension birdcc.bird2-lsp
codium --install-extension birdcc.vscode-bird2-conf
```

OpenVSX:

- https://open-vsx.org/extension/BIRDCC/bird2-extension-pack
- https://open-vsx.org/extension/birdcc/bird2-lsp
- https://open-vsx.org/extension/BIRDCC/vscode-bird2-conf

For Cursor, Windsurf, Kiro, Trae, code-server, or another fork, first verify that its CLI supports
`--install-extension` and that its configured registry contains the requested IDs. Do not assume
all forks use the same registry.

## Neovim

`BIRD.nvim` was renamed from `BIRD2.nvim`. New lazy.nvim configuration must load it before
filetype detection; `ft = "bird2"` creates a detection/loading cycle and must not be used:

```lua
{
  "bird-chinese-community/BIRD.nvim",
  version = "^1.0.14",
  lazy = false,
  config = function()
    require("bird2").setup()
  end,
}
```

The repository name changed, but `require("bird2")`, `filetype=bird2`, `:Bird2`, and
`:checkhealth bird2` remain compatible.

To add LSP features, install `@birdcc/cli` and start the server for detected BIRD buffers:

```lua
vim.api.nvim_create_autocmd("FileType", {
  pattern = "bird2",
  callback = function(args)
    local buffer_path = vim.api.nvim_buf_get_name(args.buf)
    local search_path = vim.fs.dirname(buffer_path)
    local marker = vim.fs.find({
      "bird.config.json",
      "birdcc.config.json",
      ".git",
    }, {
      path = search_path,
      upward = true,
    })[1]

    vim.lsp.start({
      name = "birdcc",
      cmd = { "birdcc", "lsp", "--stdio" },
      root_dir = marker and vim.fs.dirname(marker) or vim.fn.getcwd(),
    })
  end,
})
```

Verify with `:set filetype?`, `:checkhealth bird2`, `:LspInfo`, and a deliberate syntax error in a
non-production test file.

## Vim

`BIRD.vim` was renamed from `BIRD2.vim`:

```vim
Plug 'bird-chinese-community/BIRD.vim'
```

or:

```vim
Plugin 'bird-chinese-community/BIRD.vim'
```

The runtime `bird2` filetype remains compatible. Verify with `:set filetype?`. Use `birdcc lint`
and `birdcc fmt --check` from the terminal for parser-backed tooling.

## Legacy Vim/Neovim checkout migration

GitHub redirects old repository URLs, but update the configured repository name. For native
packages, rename the checkout and change its remote:

```bash
git -C /path/to/BIRD2.nvim remote set-url origin \
  https://github.com/bird-chinese-community/BIRD.nvim.git
git -C /path/to/BIRD2.nvim pull --ff-only
```

Use the analogous `BIRD.vim` URL for Vim. A checkout directory may keep its old name, but plugin
manager configuration should use the new repository.

## JetBrains

There is no verified native `dev.birdcc.idea` plugin. Import the maintained TextMate grammar:

1. Download `birdcc.vscode-bird2-conf` from Marketplace/OpenVSX as a `.vsix`.
2. Unzip it and locate the directory containing its `package.json`.
3. Open **Settings/Preferences → Editor → TextMate Bundles**.
4. Add that directory and enable the `bird2` language.
5. Use `birdcc` in the terminal for linting, formatting, and native validation.

This provides highlighting only, not native JetBrains LSP integration.
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated 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: 323kUpdated Claude CodeCodexVerifiedInstall