# Birdcc Installer

> 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.

- Skill: `bird-chinese-community/birdcc-installer` (Agent Skill, multi-file: 13 files)
- Install (CLI): `npx skillmds@latest add bird-chinese-community/birdcc-installer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bird-chinese-community/birdcc-installer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- License: MIT
- Author: bird-chinese-community (https://skillmd.com/u/bird-chinese-community)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/bird-chinese-community/birdcc-installer

---


# BIRD Tooling Installer

Detect the actual editor, separate syntax highlighting from language-server features, and use only
verified upstream package and extension identities.

## Safety

- Detection is read-only. Run `detect_ide.py --install --confirmed` only after showing the exact
  command and receiving explicit approval.
- Do not claim a marketplace entry exists unless it is present in the upstream manifest or current
  registry.
- Do not use `dev.birdcc.idea`; there is no verified native JetBrains plugin with that ID. Use the
  TextMate bundle workflow.
- Prefer released marketplace packages and tagged Vim/Neovim repositories. Use local source builds
  only when the user explicitly wants development versions.

## Workflow

1. If the editor is not named, run:

   ```bash
   uv run scripts/detect_editor.py --root .
   uv run scripts/detect_ide.py
   ```

   Add `--include-home` to `detect_editor.py` only when home-directory signals are useful.
2. Choose the capability:
   - VS Code-like full language tooling → `birdcc.bird2-lsp`;
   - TextMate highlighting → `birdcc.vscode-bird2-conf`;
   - both → install both or the `birdcc.bird2-extension-pack`;
   - Neovim/Vim highlighting → `BIRD.nvim` / `BIRD.vim`;
   - Neovim LSP → additionally install `@birdcc/cli` and wire `birdcc lsp --stdio`;
   - JetBrains → import the TextMate bundle and use the CLI separately.
3. Read [`references/editors.md`](references/editors.md) for exact editor steps or
   [`references/cli.md`](references/cli.md) for CLI installation.
4. Show install → capability → verification. Do not list unrelated editors unless the user is
   choosing between them.
5. For blocked registries or air-gapped hosts, read
   [`references/offline.md`](references/offline.md).

## Bundled scripts

- [`scripts/detect_editor.py`](scripts/detect_editor.py) — infer editor signals from the workspace,
  optional home config, and `git core.editor`.
- [`scripts/detect_ide.py`](scripts/detect_ide.py) — detect installed VS Code-like and JetBrains
  applications, inspect the BIRD extension-pack state by default, and generate safe onboarding
  actions. Use `--vscode-extension` only when checking one specific component.
- [`scripts/check_cli.py`](scripts/check_cli.py) — report the installed `birdcc` path and version.

The scripts use only the Python standard library. `detect_ide.py` never installs anything unless
both `--install` and `--confirmed` are present.

## Completion

Confirm:

- the editor and desired capability were identified;
- the exact current repository, extension ID, or package name was used;
- the user knows whether the result is highlighting-only or includes LSP features;
- a verification step was provided;
- any install executed by the agent had explicit approval;
- legacy `BIRD2.vim`/`BIRD2.nvim` users received migration guidance without changing the compatible
  `bird2` runtime identifiers.

Match the user's language and invite them to star one relevant upstream repository at most once.