[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NVX04KYKK0QWSW2CHSC9D9":3,"skill-same:01M6NVX04KYKK0QWSW2CHSC9D9":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M6NVX04KYKK0QWSW2CHSC9D9","dependabot",null,"Comprehensive guide for configuring and managing GitHub Dependabot. Use this skill when users ask about creating or optimizing dependabot.yml files, managing Dependabot pull requests, configuring dependency update strategies, setting up grouped updates, monorepo patterns, multi-ecosystem groups, security update configuration, auto-triage rules, or any GitHub Advanced Security (GHAS) supply chain security topic related to Dependabot.","mattonweb\u002Fai-assistant-foundry","mattonweb","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2309734?v=4","01M6NQYCY846TKYN2ZCRS71WQ7","Matt Johnson","01M6NQYD2NPAQEFVD8TW9W0SVX",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fdevops-cicd\u002Fgithub\u002Fdependabot\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"dependency","updates","ecosystem","supply","advanced","chain","strategies","patterns","files","up","security","auto","guide","ask","monorepo","pull","update","dependency update","pull requests","2026-11-10 10:12:30",false,"---\nname: dependabot\ndescription: >-\n  Comprehensive guide for configuring and managing GitHub Dependabot. Use this skill when\n  users ask about creating or optimizing dependabot.yml files, managing Dependabot pull requests,\n  configuring dependency update strategies, setting up grouped updates, monorepo patterns,\n  multi-ecosystem groups, security update configuration, auto-triage rules, or any GitHub\n  Advanced Security (GHAS) supply chain security topic related to Dependabot.\n---\n\n# Dependabot Configuration & Management\n\n## Overview\n\nDependabot is GitHub's built-in dependency management tool with three core capabilities:\n\n1. **Dependabot Alerts** — Notify when dependencies have known vulnerabilities (CVEs)\n2. **Dependabot Security Updates** — Auto-create PRs to fix vulnerable dependencies\n3. **Dependabot Version Updates** — Auto-create PRs to keep dependencies current\n\nAll configuration lives in a **single file**: `.github\u002Fdependabot.yml` on the default branch. GitHub does **not** support multiple `dependabot.yml` files per repository.\n\n## Configuration Workflow\n\nFollow this process when creating or optimizing a `dependabot.yml`:\n\n### Step 1: Detect All Ecosystems\n\nScan the repository for dependency manifests. Look for:\n\n| Ecosystem | YAML Value | Manifest Files |\n|---|---|---|\n| npm\u002Fpnpm\u002Fyarn | `npm` | `package.json`, `package-lock.json`, `pnpm-lock.yaml`, `yarn.lock` |\n| pip\u002Fpipenv\u002Fpoetry\u002Fuv | `pip` | `requirements.txt`, `Pipfile`, `pyproject.toml`, `setup.py` |\n| Docker | `docker` | `Dockerfile` |\n| Docker Compose | `docker-compose` | `docker-compose.yml` |\n| GitHub Actions | `github-actions` | `.github\u002Fworkflows\u002F*.yml` |\n| Go modules | `gomod` | `go.mod` |\n| Bundler (Ruby) | `bundler` | `Gemfile` |\n| Cargo (Rust) | `cargo` | `Cargo.toml` |\n| Composer (PHP) | `composer` | `composer.json` |\n| NuGet (.NET) | `nuget` | `*.csproj`, `packages.config` |\n| .NET SDK | `dotnet-sdk` | `global.json` |\n| Maven (Java) | `maven` | `pom.xml` |\n| Gradle (Java) | `gradle` | `build.gradle` |\n| Terraform | `terraform` | `*.tf` |\n| OpenTofu | `opentofu` | `*.tf` |\n| Helm | `helm` | `Chart.yaml` |\n| Hex (Elixir) | `mix` | `mix.exs` |\n| Swift | `swift` | `Package.swift` |\n| Pub (Dart) | `pub` | `pubspec.yaml` |\n| Bun | `bun` | `bun.lockb` |\n| Dev Containers | `devcontainers` | `devcontainer.json` |\n| Git Submodules | `gitsubmodule` | `.gitmodules` |\n| Pre-commit | `pre-commit` | `.pre-commit-config.yaml` |\n\nNote: pnpm and yarn both use the `npm` ecosystem value.\n\n### Step 2: Map Directory Locations\n\nFor each ecosystem, identify where manifests live. Use `directories` (plural) with glob patterns for monorepos:\n\n```yaml\ndirectories:\n  - \"\u002F\"           # root\n  - \"\u002Fapps\u002F*\"     # all app subdirs\n  - \"\u002Fpackages\u002F*\" # all package subdirs\n  - \"\u002Flib-*\"      # dirs starting with lib-\n  - \"**\u002F*\"        # recursive (all subdirs)\n```\n\nImportant: `directory` (singular) does NOT support globs. Use `directories` (plural) for wildcards.\n\n### Step 3: Configure Each Ecosystem Entry\n\nEvery entry needs at minimum:\n\n```yaml\n- package-ecosystem: \"npm\"\n  directory: \"\u002F\"\n  schedule:\n    interval: \"weekly\"\n```\n\n### Step 4: Optimize with Grouping, Labels, and Scheduling\n\nSee sections below for each optimization technique.\n\n## Monorepo Strategies\n\n### Glob Patterns for Workspace Coverage\n\nFor monorepos with many packages, use glob patterns to avoid listing each directory:\n\n```yaml\n- package-ecosystem: \"npm\"\n  directories:\n    - \"\u002F\"\n    - \"\u002Fapps\u002F*\"\n    - \"\u002Fpackages\u002F*\"\n    - \"\u002Fservices\u002F*\"\n  schedule:\n    interval: \"weekly\"\n```\n\n### Cross-Directory Grouping\n\nUse `group-by: dependency-name` to create a single PR when the same dependency updates across multiple directories:\n\n```yaml\ngroups:\n  monorepo-deps:\n    group-by: dependency-name\n```\n\nThis creates one PR per dependency across all specified directories, reducing CI costs and review burden.\n\nLimitations:\n- All directories must use the same package ecosystem\n- Applies to version updates only\n- Incompatible version constraints create separate PRs\n\n### Standalone Packages Outside Workspaces\n\nIf a directory has its own lockfile and is NOT part of the workspace (e.g., scripts in `.github\u002F`), create a separate ecosystem entry for it.\n\n## Dependency Grouping\n\nReduce PR noise by grouping related dependencies into single PRs.\n\n### By Dependency Type\n\n```yaml\ngroups:\n  dev-dependencies:\n    dependency-type: \"development\"\n    update-types: [\"minor\", \"patch\"]\n  production-dependencies:\n    dependency-type: \"production\"\n    update-types: [\"minor\", \"patch\"]\n```\n\n### By Name Pattern\n\n```yaml\ngroups:\n  angular:\n    patterns: [\"@angular*\"]\n    update-types: [\"minor\", \"patch\"]\n  testing:\n    patterns: [\"jest*\", \"@testing-library*\", \"ts-jest\"]\n```\n\n### For Security Updates\n\n```yaml\ngroups:\n  security-patches:\n    applies-to: security-updates\n    patterns: [\"*\"]\n    update-types: [\"patch\", \"minor\"]\n```\n\nKey behaviors:\n- Dependencies matching multiple groups go to the **first** match\n- `applies-to` defaults to `version-updates` when absent\n- Ungrouped dependencies get individual PRs\n\n## Multi-Ecosystem Groups\n\nCombine updates across different package ecosystems into a single PR:\n\n```yaml\nversion: 2\n\nmulti-ecosystem-groups:\n  infrastructure:\n    schedule:\n      interval: \"weekly\"\n    labels: [\"infrastructure\", \"dependencies\"]\n\nupdates:\n  - package-ecosystem: \"docker\"\n    directory: \"\u002F\"\n    patterns: [\"nginx\", \"redis\"]\n    multi-ecosystem-group: \"infrastructure\"\n\n  - package-ecosystem: \"terraform\"\n    directory: \"\u002F\"\n    patterns: [\"aws*\"]\n    multi-ecosystem-group: \"infrastructure\"\n```\n\nThe `patterns` key is required when using `multi-ecosystem-group`.\n\n## PR Customization\n\n### Labels\n\n```yaml\nlabels:\n  - \"dependencies\"\n  - \"npm\"\n```\n\nSet `labels: []` to disable all labels including defaults. SemVer labels (`major`, `minor`, `patch`) are always applied if present in the repo.\n\n### Commit Messages\n\n```yaml\ncommit-message:\n  prefix: \"deps\"\n  prefix-development: \"deps-dev\"\n  include: \"scope\"  # adds deps\u002Fdeps-dev scope after prefix\n```\n\n### Assignees and Milestones\n\n```yaml\nassignees: [\"security-team-lead\"]\nmilestone: 4  # numeric ID from milestone URL\n```\n\n### Branch Name Separator\n\n```yaml\npull-request-branch-name:\n  separator: \"-\"  # default is \u002F\n```\n\n### Target Branch\n\n```yaml\ntarget-branch: \"develop\"  # PRs target this instead of default branch\n```\n\nNote: When `target-branch` is set, security updates still target the default branch; all ecosystem config only applies to version updates.\n\n## Schedule Optimization\n\n### Intervals\n\nSupported: `daily`, `weekly`, `monthly`, `quarterly`, `semiannually`, `yearly`, `cron`\n\n```yaml\nschedule:\n  interval: \"weekly\"\n  day: \"monday\"         # for weekly only\n  time: \"09:00\"         # HH:MM format\n  timezone: \"America\u002FNew_York\"\n```\n\n### Cron Expressions\n\n```yaml\nschedule:\n  interval: \"cron\"\n  cronjob: \"0 9 * * 1\"  # Every Monday at 9 AM\n```\n\n### Cooldown Periods\n\nDelay updates for newly released versions to avoid early-adopter issues:\n\n```yaml\ncooldown:\n  default-days: 5\n  semver-major-days: 30\n  semver-minor-days: 7\n  semver-patch-days: 3\n  include: [\"*\"]\n  exclude: [\"critical-lib\"]\n```\n\nCooldown applies to version updates only, not security updates.\n\n## Security Updates Configuration\n\n### Enable via Repository Settings\n\nSettings → Advanced Security → Enable Dependabot alerts, security updates, and grouped security updates.\n\n### Group Security Updates in YAML\n\n```yaml\ngroups:\n  security-patches:\n    applies-to: security-updates\n    patterns: [\"*\"]\n    update-types: [\"patch\", \"minor\"]\n```\n\n### Disable Version Updates (Security Only)\n\n```yaml\nopen-pull-requests-limit: 0  # disables version update PRs\n```\n\n### Auto-Triage Rules\n\nGitHub presets auto-dismiss low-impact alerts for development dependencies. Custom rules can filter by severity, package name, CWE, and more. Configure in repository Settings → Advanced Security.\n\n## PR Comment Commands\n\nInteract with Dependabot PRs using `@dependabot` comments.\n\n> **Note:** As of January 2026, merge\u002Fclose\u002Freopen commands have been deprecated.\n> Use GitHub's native UI, CLI (`gh pr merge`), or auto-merge instead.\n\n| Command | Effect |\n|---|---|\n| `@dependabot rebase` | Rebase the PR |\n| `@dependabot recreate` | Recreate the PR from scratch |\n| `@dependabot ignore this dependency` | Close and never update this dependency |\n| `@dependabot ignore this major version` | Ignore this major version |\n| `@dependabot ignore this minor version` | Ignore this minor version |\n| `@dependabot ignore this patch version` | Ignore this patch version |\n\nFor grouped PRs, additional commands:\n- `@dependabot ignore DEPENDENCY_NAME` — ignore specific dependency in group\n- `@dependabot unignore DEPENDENCY_NAME` — clear ignores, reopen with updates\n- `@dependabot unignore *` — clear all ignores for all dependencies in group\n- `@dependabot show DEPENDENCY_NAME ignore conditions` — display current ignores\n\nFor the complete command reference, see `references\u002Fpr-commands.md`.\n\n## Ignore and Allow Rules\n\n### Ignore Specific Dependencies\n\n```yaml\nignore:\n  - dependency-name: \"lodash\"\n  - dependency-name: \"@types\u002Fnode\"\n    update-types: [\"version-update:semver-patch\"]\n  - dependency-name: \"express\"\n    versions: [\"5.x\"]\n```\n\n### Allow Only Specific Types\n\n```yaml\nallow:\n  - dependency-type: \"production\"\n  - dependency-name: \"express\"\n```\n\nRule: If a dependency matches both `allow` and `ignore`, it is **ignored**.\n\n### Exclude Paths\n\n```yaml\nexclude-paths:\n  - \"vendor\u002F**\"\n  - \"test\u002Ffixtures\u002F**\"\n```\n\n## Advanced Options\n\n### Versioning Strategy\n\nControls how Dependabot edits version constraints:\n\n| Value | Behavior |\n|---|---|\n| `auto` | Default — increase for apps, widen for libraries |\n| `increase` | Always increase minimum version |\n| `increase-if-necessary` | Only change if current range excludes new version |\n| `lockfile-only` | Only update lockfiles, ignore manifests |\n| `widen` | Widen range to include both old and new versions |\n\n### Rebase Strategy\n\n```yaml\nrebase-strategy: \"disabled\"  # stop auto-rebasing\n```\n\nAllow rebase over extra commits by including `[dependabot skip]` in commit messages.\n\n### Open PR Limit\n\n```yaml\nopen-pull-requests-limit: 10  # default is 5 for version, 10 for security\n```\n\nSet to `0` to disable version updates entirely.\n\n### Private Registries\n\n```yaml\nregistries:\n  npm-private:\n    type: npm-registry\n    url: https:\u002F\u002Fnpm.example.com\n    token: ${{secrets.NPM_TOKEN}}\n\nupdates:\n  - package-ecosystem: \"npm\"\n    directory: \"\u002F\"\n    registries:\n      - npm-private\n```\n\n## FAQ\n\n**Can I have multiple `dependabot.yml` files?**\nNo. GitHub supports exactly one file at `.github\u002Fdependabot.yml`. Use multiple `updates` entries within that file for different ecosystems and directories.\n\n**Does Dependabot support pnpm?**\nYes. Use `package-ecosystem: \"npm\"` — Dependabot detects `pnpm-lock.yaml` automatically.\n\n**How do I reduce PR noise in a monorepo?**\nUse `groups` to batch updates, `directories` with globs for coverage, and `group-by: dependency-name` for cross-directory grouping. Consider `monthly` or `quarterly` intervals for low-priority ecosystems.\n\n**How do I handle dependencies outside the workspace?**\nCreate a separate ecosystem entry with its own `directory` pointing to that location.\n\n## Resources\n\n- `references\u002Fdependabot-yml-reference.md` — Complete YAML options reference\n- `references\u002Fpr-commands.md` — Full PR comment commands reference\n- `references\u002Fexample-configs.md` — Real-world configuration examples\n","# Dependabot Configuration & Management\n\n## Overview\n\nDependabot is GitHub's built-in dependency management tool with three core capabilities:\n\n1. **Dependabot Alerts** — Notify when dependencies have known vulnerabilities (CVEs)\n2. **Dependabot Security Updates** — Auto-create PRs to fix vulnerable dependencies\n3. **Dependabot Version Updates** — Auto-create PRs to keep dependencies current\n\nAll configuration lives in a **single file**: `.github\u002Fdependabot.yml` on the default branch. GitHub does **not** support multiple `dependabot.yml` files per repository.\n\n## Configuration Workflow\n\nFollow this process when creating or optimizing a `dependabot.yml`:\n\n### Step 1: Detect All Ecosystems\n\nScan the repository for dependency manifests. Look for:\n\n| Ecosystem | YAML Value | Manifest Files |\n|---|---|---|\n| npm\u002Fpnpm\u002Fyarn | `npm` | `package.json`, `package-lock.json`, `pnpm-lock.yaml`, `yarn.lock` |\n| pip\u002Fpipenv\u002Fpoetry\u002Fuv | `pip` | `requirements.txt`, `Pipfile`, `pyproject.toml`, `setup.py` |\n| Docker | `docker` | `Dockerfile` |\n| Docker Compose | `docker-compose` | `docker-compose.yml` |\n| GitHub Actions | `github-actions` | `.github\u002Fworkflows\u002F*.yml` |\n| Go modules | `gomod` | `go.mod` |\n| Bundler (Ruby) | `bundler` | `Gemfile` |\n| Cargo (Rust) | `cargo` | `Cargo.toml` |\n| Composer (PHP) | `composer` | `composer.json` |\n| NuGet (.NET) | `nuget` | `*.csproj`, `packages.config` |\n| .NET SDK | `dotnet-sdk` | `global.json` |\n| Maven (Java) | `maven` | `pom.xml` |\n| Gradle (Java) | `gradle` | `build.gradle` |\n| Terraform | `terraform` | `*.tf` |\n| OpenTofu | `opentofu` | `*.tf` |\n| Helm | `helm` | `Chart.yaml` |\n| Hex (Elixir) | `mix` | `mix.exs` |\n| Swift | `swift` | `Package.swift` |\n| Pub (Dart) | `pub` | `pubspec.yaml` |\n| Bun | `bun` | `bun.lockb` |\n| Dev Containers | `devcontainers` | `devcontainer.json` |\n| Git Submodules | `gitsubmodule` | `.gitmodules` |\n| Pre-commit | `pre-commit` | `.pre-commit-config.yaml` |\n\nNote: pnpm and yarn both use the `npm` ecosystem value.\n\n### Step 2: Map Directory Locations\n\nFor each ecosystem, identify where manifests live. Use `directories` (plural) with glob patterns for monorepos:\n\n```yaml\ndirectories:\n  - \"\u002F\"           # root\n  - \"\u002Fapps\u002F*\"     # all app subdirs\n  - \"\u002Fpackages\u002F*\" # all package subdirs\n  - \"\u002Flib-*\"      # dirs starting with lib-\n  - \"**\u002F*\"        # recursive (all subdirs)\n```\n\nImportant: `directory` (singular) does NOT support globs. Use `directories` (plural) for wildcards.\n\n### Step 3: Configure Each Ecosystem Entry\n\nEvery entry needs at minimum:\n\n```yaml\n- package-ecosystem: \"npm\"\n  directory: \"\u002F\"\n  schedule:\n    interval: \"weekly\"\n```\n\n### Step 4: Optimize with Grouping, Labels, and Scheduling\n\nSee sections below for each optimization technique.\n\n## Monorepo Strategies\n\n### Glob Patterns for Workspace Coverage\n\nFor monorepos with many packages, use glob patterns to avoid listing each directory:\n\n```yaml\n- package-ecosystem: \"npm\"\n  directories:\n    - \"\u002F\"\n    - \"\u002Fapps\u002F*\"\n    - \"\u002Fpackages\u002F*\"\n    - \"\u002Fservices\u002F*\"\n  schedule:\n    interval: \"weekly\"\n```\n\n### Cross-Directory Grouping\n\nUse `group-by: dependency-name` to create a single PR when the same dependency updates across multiple directories:\n\n```yaml\ngroups:\n  monorepo-deps:\n    group-by: dependency-name\n```\n\nThis creates one PR per dependency across all specified directories, reducing CI costs and review burden.\n\nLimitations:\n- All directories must use the same package ecosystem\n- Applies to version updates only\n- Incompatible version constraints create separate PRs\n\n### Standalone Packages Outside Workspaces\n\nIf a directory has its own lockfile and is NOT part of the workspace (e.g., scripts in `.github\u002F`), create a separate ecosystem entry for it.\n\n## Dependency Grouping\n\nReduce PR noise by grouping related dependencies into single PRs.\n\n### By Dependency Type\n\n```yaml\ngroups:\n  dev-dependencies:\n    dependency-type: \"development\"\n    update-types: [\"minor\", \"patch\"]\n  production-dependencies:\n    dependency-type: \"production\"\n    update-types: [\"minor\", \"patch\"]\n```\n\n### By Name Pattern\n\n```yaml\ngroups:\n  angular:\n    patterns: [\"@angular*\"]\n    update-types: [\"minor\", \"patch\"]\n  testing:\n    patterns: [\"jest*\", \"@testing-library*\", \"ts-jest\"]\n```\n\n### For Security Updates\n\n```yaml\ngroups:\n  security-patches:\n    applies-to: security-updates\n    patterns: [\"*\"]\n    update-types: [\"patch\", \"minor\"]\n```\n\nKey behaviors:\n- Dependencies matching multiple groups go to the **first** match\n- `applies-to` defaults to `version-updates` when absent\n- Ungrouped dependencies get individual PRs\n\n## Multi-Ecosystem Groups\n\nCombine updates across different package ecosystems into a single PR:\n\n```yaml\nversion: 2\n\nmulti-ecosystem-groups:\n  infrastructure:\n    schedule:\n      interval: \"weekly\"\n    labels: [\"infrastructure\", \"dependencies\"]\n\nupdates:\n  - package-ecosystem: \"docker\"\n    directory: \"\u002F\"\n    patterns: [\"nginx\", \"redis\"]\n    multi-ecosystem-group: \"infrastructure\"\n\n  - package-ecosystem: \"terraform\"\n    directory: \"\u002F\"\n    patterns: [\"aws*\"]\n    multi-ecosystem-group: \"infrastructure\"\n```\n\nThe `patterns` key is required when using `multi-ecosystem-group`.\n\n## PR Customization\n\n### Labels\n\n```yaml\nlabels:\n  - \"dependencies\"\n  - \"npm\"\n```\n\nSet `labels: []` to disable all labels including defaults. SemVer labels (`major`, `minor`, `patch`) are always applied if present in the repo.\n\n### Commit Messages\n\n```yaml\ncommit-message:\n  prefix: \"deps\"\n  prefix-development: \"deps-dev\"\n  include: \"scope\"  # adds deps\u002Fdeps-dev scope after prefix\n```\n\n### Assignees and Milestones\n\n```yaml\nassignees: [\"security-team-lead\"]\nmilestone: 4  # numeric ID from milestone URL\n```\n\n### Branch Name Separator\n\n```yaml\npull-request-branch-name:\n  separator: \"-\"  # default is \u002F\n```\n\n### Target Branch\n\n```yaml\ntarget-branch: \"develop\"  # PRs target this instead of default branch\n```\n\nNote: When `target-branch` is set, security updates still target the default branch; all ecosystem config only applies to version updates.\n\n## Schedule Optimization\n\n### Intervals\n\nSupported: `daily`, `weekly`, `monthly`, `quarterly`, `semiannually`, `yearly`, `cron`\n\n```yaml\nschedule:\n  interval: \"weekly\"\n  day: \"monday\"         # for weekly only\n  time: \"09:00\"         # HH:MM format\n  timezone: \"America\u002FNew_York\"\n```\n\n### Cron Expressions\n\n```yaml\nschedule:\n  interval: \"cron\"\n  cronjob: \"0 9 * * 1\"  # Every Monday at 9 AM\n```\n\n### Cooldown Periods\n\nDelay updates for newly released versions to avoid early-adopter issues:\n\n```yaml\ncooldown:\n  default-days: 5\n  semver-major-days: 30\n  semver-minor-days: 7\n  semver-patch-days: 3\n  include: [\"*\"]\n  exclude: [\"critical-lib\"]\n```\n\nCooldown applies to version updates only, not security updates.\n\n## Security Updates Configuration\n\n### Enable via Repository Settings\n\nSettings → Advanced Security → Enable Dependabot alerts, security updates, and grouped security updates.\n\n### Group Security Updates in YAML\n\n```yaml\ngroups:\n  security-patches:\n    applies-to: security-updates\n    patterns: [\"*\"]\n    update-types: [\"patch\", \"minor\"]\n```\n\n### Disable Version Updates (Security Only)\n\n```yaml\nopen-pull-requests-limit: 0  # disables version update PRs\n```\n\n### Auto-Triage Rules\n\nGitHub presets auto-dismiss low-impact alerts for development dependencies. Custom rules can filter by severity, package name, CWE, and more. Configure in repository Settings → Advanced Security.\n\n## PR Comment Commands\n\nInteract with Dependabot PRs using `@dependabot` comments.\n\n> **Note:** As of January 2026, merge\u002Fclose\u002Freopen commands have been deprecated.\n> Use GitHub's native UI, CLI (`gh pr merge`), or auto-merge instead.\n\n| Command | Effect |\n|---|---|\n| `@dependabot rebase` | Rebase the PR |\n| `@dependabot recreate` | Recreate the PR from scratch |\n| `@dependabot ignore this dependency` | Close and never update this dependency |\n| `@dependabot ignore this major version` | Ignore this major version |\n| `@dependabot ignore this minor version` | Ignore this minor version |\n| `@dependabot ignore this patch version` | Ignore this patch version |\n\nFor grouped PRs, additional commands:\n- `@dependabot ignore DEPENDENCY_NAME` — ignore specific dependency in group\n- `@dependabot unignore DEPENDENCY_NAME` — clear ignores, reopen with updates\n- `@dependabot unignore *` — clear all ignores for all dependencies in group\n- `@dependabot show DEPENDENCY_NAME ignore conditions` — display current ignores\n\nFor the complete command reference, see `references\u002Fpr-commands.md`.\n\n## Ignore and Allow Rules\n\n### Ignore Specific Dependencies\n\n```yaml\nignore:\n  - dependency-name: \"lodash\"\n  - dependency-name: \"@types\u002Fnode\"\n    update-types: [\"version-update:semver-patch\"]\n  - dependency-name: \"express\"\n    versions: [\"5.x\"]\n```\n\n### Allow Only Specific Types\n\n```yaml\nallow:\n  - dependency-type: \"production\"\n  - dependency-name: \"express\"\n```\n\nRule: If a dependency matches both `allow` and `ignore`, it is **ignored**.\n\n### Exclude Paths\n\n```yaml\nexclude-paths:\n  - \"vendor\u002F**\"\n  - \"test\u002Ffixtures\u002F**\"\n```\n\n## Advanced Options\n\n### Versioning Strategy\n\nControls how Dependabot edits version constraints:\n\n| Value | Behavior |\n|---|---|\n| `auto` | Default — increase for apps, widen for libraries |\n| `increase` | Always increase minimum version |\n| `increase-if-necessary` | Only change if current range excludes new version |\n| `lockfile-only` | Only update lockfiles, ignore manifests |\n| `widen` | Widen range to include both old and new versions |\n\n### Rebase Strategy\n\n```yaml\nrebase-strategy: \"disabled\"  # stop auto-rebasing\n```\n\nAllow rebase over extra commits by including `[dependabot skip]` in commit messages.\n\n### Open PR Limit\n\n```yaml\nopen-pull-requests-limit: 10  # default is 5 for version, 10 for security\n```\n\nSet to `0` to disable version updates entirely.\n\n### Private Registries\n\n```yaml\nregistries:\n  npm-private:\n    type: npm-registry\n    url: https:\u002F\u002Fnpm.example.com\n    token: ${{secrets.NPM_TOKEN}}\n\nupdates:\n  - package-ecosystem: \"npm\"\n    directory: \"\u002F\"\n    registries:\n      - npm-private\n```\n\n## FAQ\n\n**Can I have multiple `dependabot.yml` files?**\nNo. GitHub supports exactly one file at `.github\u002Fdependabot.yml`. Use multiple `updates` entries within that file for different ecosystems and directories.\n\n**Does Dependabot support pnpm?**\nYes. Use `package-ecosystem: \"npm\"` — Dependabot detects `pnpm-lock.yaml` automatically.\n\n**How do I reduce PR noise in a monorepo?**\nUse `groups` to batch updates, `directories` with globs for coverage, and `group-by: dependency-name` for cross-directory grouping. Consider `monthly` or `quarterly` intervals for low-priority ecosystems.\n\n**How do I handle dependencies outside the workspace?**\nCreate a separate ecosystem entry with its own `directory` pointing to that location.\n\n## Resources\n\n- `references\u002Fdependabot-yml-reference.md` — Complete YAML options reference\n- `references\u002Fpr-commands.md` — Full PR comment commands reference\n- `references\u002Fexample-configs.md` — Real-world configuration examples\n",{"name":5,"description":7},"main","d8518247cb8ab8b2dac57a6be33543ffd23b97c5","devops-cicd\u002Fgithub\u002Fdependabot",0,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry","https:\u002F\u002Fgithub.com\u002Fmattonweb","2026-05-29 08:42:23",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add mattonweb\u002Fai-assistant-foundry --skill dependabot",{"tool":56,"command":57},"bunx","bunx skills add mattonweb\u002Fai-assistant-foundry --skill dependabot",{"tool":59,"command":60},"pnpm","pnpm dlx skills add mattonweb\u002Fai-assistant-foundry --skill dependabot","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fdevops-cicd\u002Fgithub\u002Fdependabot\u002FSKILL.md",true,[64,70,74],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fdependabot-yml-reference.md","REFERENCE","参考文档",9728,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fdevops-cicd\u002Fgithub\u002Fdependabot\u002Freferences\u002Fdependabot-yml-reference.md",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fexample-configs.md",8186,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fdevops-cicd\u002Fgithub\u002Fdependabot\u002Freferences\u002Fexample-configs.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fpr-commands.md",4296,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fdevops-cicd\u002Fgithub\u002Fdependabot\u002Freferences\u002Fpr-commands.md",[79,116,129,149,170,196],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":95,"publishedAt":38},"01M6P02DENRHN6KVGYC55FKASJ","writing-clearly-and-concisely","Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[85,90],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115],"writing clearly and concisely","writing","concisely","text","for","more","timeless","error","professional","prose","reports","use","read","Rules","commit messages","messages","error messages","ui","documentation","commit",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":38},"01M6P0286HZ8RWMFCCPC8HF7SC","crafting-effective-readmes","Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fcrafting-effective-readmes\u002FSKILL.md",[],[123,124,97,125,126,107,127,128,27],"crafting effective readmes","README","templates","type","project","guidance",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":138,"publishedAt":38},"01M6P025A41BBTPWVTZ3GFQVG6","wiki-architect","You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Fwiki-architect\u002FSKILL.md",[135],{"categoryNo":136,"categoryName":137,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000038","人力资源",[139,140,141,142,143,144,145,146,147,148,114],"wiki","architect","wiki architect","unknown","you","documentation architect","guides","structured","community","onboarding",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":38},"01M6P01NSKPXP77NWB4K0PXRK5","readme","You are an expert technical writer creating comprehensive project documentation. Your goal is to write a README.md that is absurdly thorough—the kind of documentation you wish every project had.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Freadme\u002FSKILL.md",[],[124,156,157,158,143,159,160,127,161,162,43,163,164,165,166,167,114,168,169],"project documentation","tree","kind","expert","github","wish","writer","goal","write","technical writer","technical","https","write a readme","safe",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":38},"01M6P01GP0NEN8KT3A3SA6ZFVE","ubiquitous-language","Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions \"domain model\" or \"DDD\".","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattpocock\u002Fubiquitous-language\u002FSKILL.md",[],[177,178,107,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195],"ubiquitous language","language","extract","user","glossary","model","terms","ddd","create","build","true","canonical","style","define","harden","domain model","domain","terminology","conversation",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":204,"publishedAt":38},"01M6P01BJBP9XP4TDRT7QD1ZVA","technical-writing-style","Enforce clear, direct writing in software development documents including OKRs, PRDs, tech specs, architecture decision records (ADRs), git commit messages, PR descriptions, READMEs, changelogs, runbooks, incident postmortems, API docs, and onboarding guides. Trigger whenever a user asks to write, edit, revise, or review any of these document types. Also trigger when the user says writing \"sounds like AI\", \"feels robotic\", \"needs polish\", or asks to \"make it sound more natural\" in the context of technical or professional prose. Do not trigger for fiction, poetry, creative writing, academic papers, or legal documents unless the user explicitly asks for a more natural tone.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattnebr\u002Ftechnical-writing-style\u002FSKILL.md",[202,203],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},[205,206,189,166,97,207,104,208,209,210,211,212,213,214,215,111,216,217,115,218],"writing style","technical writing style","technical writing","papers","types","runbooks","software development","incident","Poetry","decision","api","documents","architecture","review"]