biome-vcs-integration
Configure Biome to respect .gitignore via VCS integration so that untracked and ignored files are skipped during format and lint. Use when the user encounters Biome errors on .gitignore'd files, CI failures from local-only files, or asks how to exclude files from Biome. Trigger on keywords: "biome gitignore", "biome ignore files", "biome vcs", "biome skip untracked", "biome CI failure local file", "biome settings.local.json", "useIgnoreFile", "clientKind".
What this skill does
# Biome VCS Integration
## Problem
Biome does **not** automatically skip `.gitignore`'d files. This causes CI
failures and false positives when local-only files (e.g.,
`.claude/settings.local.json`) don't match Biome's formatting rules.
The fix is non-obvious: you need to enable Biome's VCS integration explicitly
in `biome.json`.
## Diagnosis
Check for these symptoms before applying the fix:
1. Biome reports errors on files that are listed in `.gitignore`.
2. CI fails on files that only exist locally (untracked).
3. Running `biome check` or `biome format` processes files you expected to be
ignored.
Verify with:
```bash
# Check if the file causing errors is gitignored
git check-ignore -v <problematic-file>
```
If `git check-ignore` confirms the file is ignored but Biome still processes
it, VCS integration is the fix.
## Fix
### Step 1 — Enable VCS integration in biome.json
Add or merge the `vcs` section into the project's `biome.json` (or
`biome.jsonc`):
```json
{
"vcs": {
"enabled": true,
"clientKind": "git",
"useIgnoreFile": true
}
}
```
**Important:** The `clientKind` field is **required**. Omitting it causes a
Biome config validation error.
### Step 2 — Remove redundant manual exclusions (if any)
With VCS integration enabled, manual exclusions for `.gitignore`'d paths are
redundant. Check the `files` section for patterns that duplicate `.gitignore`
entries and remove them.
**Biome v1.x** — uses the `ignore` key:
```json
{
"files": {
"ignore": [".claude/settings.local.json"]
}
}
```
Remove entries that `.gitignore` already covers.
**Biome v2.x** — uses `includes` with `!` negation patterns (the old `ignore`
key no longer exists):
```json
{
"files": {
"includes": ["**", "!.claude/settings.local.json"]
}
}
```
**Note:** A standalone `!` negation pattern (e.g., `["!path"]`) does not work
on its own — it requires an earlier include pattern like `"**"` to establish the
initial file set. Without it, Biome has no files to exclude from. The `!!`
double-negation prefix is a separate feature reserved for Biome's scanner-level
force-ignore behavior and should not be confused with regular `!` exclusions.
Remove `!` negation entries that `.gitignore` already covers.
### Step 3 — Verify
```bash
# Confirm Biome now skips gitignored files
biome check .
```
The previously-erroring gitignored files should no longer appear in output.
## Biome v2.x Migration Notes
If migrating from Biome v1.x to v2.x while applying this fix:
- `files.ignore` is replaced by `files.includes` with `!` prefix for
exclusions. Negated entries must be preceded by an include pattern (e.g.,
`["**", "!path"]`) — a standalone `["!path"]` has no effect. The `!!` prefix
is reserved for scanner-level force-ignore and is distinct from regular `!`
exclusions.
- The `vcs` config section works the same in both versions.
- Run `biome migrate` for automated config migration.
## Common Pitfalls
| Pitfall | Fix |
|---------|-----|
| Missing `clientKind` | Always include `"clientKind": "git"` — it's required |
| Nested `.gitignore` files | Biome respects nested `.gitignore` files when VCS integration is enabled; ensure `useIgnoreFile` is `true` and each subdirectory's `.gitignore` is committed |
| `biome.jsonc` vs `biome.json` | VCS config works in both; use whichever the project already has |
## Reference
- [Biome VCS integration docs](https://biomejs.dev/reference/configuration/#vcs)
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.