birdcc-installerlisted

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.
bird-chinese-community/BIRD.skills · ★ 3 · Code & Development · score 72

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

# 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`](referenc