Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion .claude/ecosystems/bash.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,5 @@ fix-cmd: null
code-fix-cmd: null
opt-in: "shellcheck and bash -n always apply to CI's shell file list"
install-hint: "shellcheck with no version pin: CI runs sudo apt-get install -y shellcheck on ubuntu-latest (pr-require-checks.yml:96, :102-103) and verifies no checksum. winget install ShellCheck.ShellCheck | brew install shellcheck. The sync-local suite also needs git and python3 (AGENTS.md:36, :97-100), and pwsh for its PowerShell half."
tool-pin: {}
gates: []
notes: "No tool-pin: CI installs Ubuntu's shellcheck package, so its version follows the runner image (pr-require-checks.yml:102-103). check-cmd lints CI's file list, not <files>: CI runs shellcheck and bash -n over scripts/*.sh and .cursor/install.sh on every change (:105-109) and leaves out .claude/cloud-bootstrap.sh, a standards-synced file (.github/workflows/pr-check-managed-files-hosted.yml:39), which <files> would lint. No --rcfile: shellcheck reads the root .shellcheckrc by itself, as in CI. CI stops at its first failing step; check-cmd runs shellcheck and bash -n over every listed file and fails when any fails. The two test steps run in order with no continue-on-error (:113-117), so CI stops at the first failure and test-cmd chains them with &&. test-sync-local.sh exits 0 when pwsh is missing: the PowerShell half reports as skipped and the bash half still runs (scripts/test-sync-local.sh:10-12, :99-100, :498-504); read its skipped count. Both suites build their fixtures under TMPDIR (scripts/test-sync-local.sh:38, scripts/test-check-docs-naming.sh:10). scripts/check-docs-naming.sh --check, the last step of the same job (:119-120), runs from cross-cutting.yaml, so a docs/ change triggers it. Glob gaps: no job in this workflow has a path filter (:15-37), so CI runs these steps on every change; these globs select only *.sh and *.bash, so a change to another file the suites read runs no local test, for example scripts/sync-local.ps1, the twin the sync-local suite runs (scripts/test-sync-local.sh:28), or .cursor-plugin/marketplace.json and the plugins/ tree, which its repo-dry-run case syncs from (:198)."
12 changes: 4 additions & 8 deletions .claude/ecosystems/cross-cutting.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -46,13 +46,9 @@ fix-cmd: null
code-fix-cmd: null
opt-in: "lychee.toml, _typos.toml and .gitleaks.toml at the repository root for lychee, typos and gitleaks; the docs-naming, jq and relative-link checks always apply"
install-hint: |
lychee 0.24.2: winget install lycheeverse.lychee | brew install lychee; CI verifies the x86_64-unknown-linux-gnu release archive by SHA-256 1f4e0ef7f6554a6ed33dd7ac144fb2e1bbed98598e7af973042fc5cd43951c9a
typos 1.50.3: winget install Crate-CI.Typos | brew install typos-cli; CI verifies the x86_64-unknown-linux-musl release archive by SHA-256 aca6b5d546307092b8d0a8e0a89dd80f9da51f2f7617c5e45c5607c1684ffbf2
gitleaks 8.30.1: winget install Gitleaks.Gitleaks | brew install gitleaks; no CI job here installs it; the gitleaks composite at ci-workflows@594987a verifies the linux_x64 release archive by SHA-256 551f6fc83ea457d62a0d98237cbad105af8d557003051f41f3e7ca7b3f2470eb
lychee at the version ci-workflows' lychee-offline action pins: winget install lycheeverse.lychee | brew install lychee
typos at the version ci-workflows' typos action pins: winget install Crate-CI.Typos | brew install typos-cli
gitleaks at the version ci-workflows' gitleaks action pins: winget install Gitleaks.Gitleaks | brew install gitleaks; no CI job here installs it
jq: winget install jqlang.jq | brew install jq; CI uses the runner's jq and installs none (pr-require-checks.yml:166-169). The relative-link check needs bash or zsh, git, sed and grep.
tool-pin:
lychee: "0.24.2"
typos: "1.50.3"
gitleaks: "8.30.1"
gates: []
notes: "Lint-only: owned by /toolchain:lint. The lychee and typos commands, versions and checksums are those of ci-workflows' lychee-offline and typos composites at the commits pr-require-checks.yml:256 and :273 pin (lychee-offline's `globs`, `config`, `exclude`, `version` and `sha256` input defaults; typos' `paths`, `config`, `hidden`, `version` and `sha256` input defaults); Dependabot moves those pins to each ci-workflows release, so compare tool-pin with those defaults when a first-party bump merges. CI passes typos hidden: true (pr-require-checks.yml:276), so typos checks dotted paths such as .github/ and .shellcheckrc, with .git/ excluded (the action's `hidden` input). CI's typos step also emits annotations from a second json pass (the action's `annotations` input, default true); that changes only the output and is left out. CI passes lychee no globs or exclude input (pr-require-checks.yml:257-258), so the defaults '**/*.md' and no --exclude-path apply (the action's `globs` and `exclude` defaults); the glob is single-quoted so lychee expands it, as in CI. Deviations: the relative-link check is CI's script with its comments dropped, its result variable named fail, not status, which zsh holds read-only, and the whole inside a subshell so its exit ends only that check; it uses process substitution, so it needs bash or zsh, not sh. CI checks each manifest with a separate jq call (:166-169); check-cmd keeps that, because one jq call over several files reads them as one stream, so two truncated files could pass together. CI stops each job at its first failing step; check-cmd runs every check. Every check reads the whole tree, not <files>: CI runs each on every change, since no job in this workflow has a path filter (:15-37), and the link checks span files, so a renamed file or heading breaks links in files the change does not touch. A local run reads the working tree, where it can raise findings CI's clean checkout does not: typos walks the tree honoring ignore files (_typos.toml:6), so an untracked file no ignore file covers is spell-checked, for example one under .work/, which .gitignore does not list (.gitignore:1-13); lychee.toml sets hidden = true and a glob input does not honor .gitignore, so ignored dot-directories other than the excluded .work/ and .claude/worktrees/ are read (lychee.toml:11-16, :47-58); the frontmatter glob in markdown.yaml expands on disk. The relative-link check and check-docs-naming.sh list files with git ls-files (pr-require-checks.yml:238; scripts/check-docs-naming.sh:40), so a new file is checked only once it is staged, and a link to an untracked file resolves locally but not in CI. Deviation from CI: gitleaks. No CI job in this repository runs gitleaks; the line keeps the local secret scan that the bundled cross-cutting default ran before this file existed (claude-code-plugins plugins/toolchain/reference/ecosystems/cross-cutting.yaml:12, opt-in :18, met by the tracked .gitleaks.toml), so these records do not switch a secret scan off. Its command, version and checksum are those of the gitleaks composite at ci-workflows@594987a (v0.39.8), which this repository does not call: gitleaks/scan.sh:113, :136 and :142 with the defaults at gitleaks/action.yml:9, :15 and :30, pins :50 (version) and :55 (checksum). gitleaks scans every file on disk under the repository root, tracked, untracked or git-ignored (a scratch file under .work/ included), and not git history; it does not read <files>. No editorconfig-checker or markdownlint command: .editorconfig, .editorconfig-checker.json and .markdownlint-cli2.jsonc are standards-synced files that CI deliberately does not re-lint (pr-require-checks.yml:7-13; pr-check-managed-files-hosted.yml:41-42, :72), and no CI job here runs those tools; lefthook.yml:1-6 pulls git hooks from claude-code-plugins, and apart from gitleaks these records follow CI, not a local hook. Not run locally: the schema step of the validate-manifests job (pr-require-checks.yml:187-200); typescript.yaml gives the reason. Checks with no local form: the pull-request contract check (pr-require-checks.yml:303-306, check-contract at the commit it pins) and the result aggregation (:307-326, aggregate-results at the same commit) in the ci-status job (:281-283); they need the pull request. This ci-status job has no draft refusal. Not run locally: the model review lanes pr-review (.github/workflows/pr-review-hosted.yml:74-85) and pr-review-security (.github/workflows/pr-review-security-hosted.yml:67-78), which review the pull request through ci-workflows reusables called at @main, not pinned; both are advisory and skip drafts (pr-review-hosted.yml:37, :76-78; pr-review-security-hosted.yml:44-46, :69-71). Not run locally: check-managed-files (pr-check-managed-files-hosted.yml:106-127, check-managed-files@944d346 v0.74.0), which needs a melodic-software/standards checkout and the pull request; it is advisory and not aggregated into ci-status (:20-22). pr-automerge-dependabot (.github/workflows/pr-automerge-dependabot.yml:22-30) checks nothing; it arms auto-merge on a Dependabot pull request (:3-8)."
notes: "Lint-only: owned by /toolchain:lint. The lychee and typos commands, versions and checksums are those of ci-workflows' lychee-offline and typos composites at the commits pr-require-checks.yml:256 and :273 pin (lychee-offline's `globs`, `config`, `exclude`, `version` and `sha256` input defaults; typos' `paths`, `config`, `hidden`, `version` and `sha256` input defaults). CI passes typos hidden: true (pr-require-checks.yml:276), so typos checks dotted paths such as .github/ and .shellcheckrc, with .git/ excluded (the action's `hidden` input). CI's typos step also emits annotations from a second json pass (the action's `annotations` input, default true); that changes only the output and is left out. CI passes lychee no globs or exclude input (pr-require-checks.yml:257-258), so the defaults '**/*.md' and no --exclude-path apply (the action's `globs` and `exclude` defaults); the glob is single-quoted so lychee expands it, as in CI. Deviations: the relative-link check is CI's script with its comments dropped, its result variable named fail, not status, which zsh holds read-only, and the whole inside a subshell so its exit ends only that check; it uses process substitution, so it needs bash or zsh, not sh. CI checks each manifest with a separate jq call (:166-169); check-cmd keeps that, because one jq call over several files reads them as one stream, so two truncated files could pass together. CI stops each job at its first failing step; check-cmd runs every check. Every check reads the whole tree, not <files>: CI runs each on every change, since no job in this workflow has a path filter (:15-37), and the link checks span files, so a renamed file or heading breaks links in files the change does not touch. A local run reads the working tree, where it can raise findings CI's clean checkout does not: typos walks the tree honoring ignore files (_typos.toml:6), so an untracked file no ignore file covers is spell-checked, for example one under .work/, which .gitignore does not list (.gitignore:1-13); lychee.toml sets hidden = true and a glob input does not honor .gitignore, so ignored dot-directories other than the excluded .work/ and .claude/worktrees/ are read (lychee.toml:11-16, :47-58); the frontmatter glob in markdown.yaml expands on disk. The relative-link check and check-docs-naming.sh list files with git ls-files (pr-require-checks.yml:238; scripts/check-docs-naming.sh:40), so a new file is checked only once it is staged, and a link to an untracked file resolves locally but not in CI. Deviation from CI: gitleaks. No CI job in this repository runs gitleaks; the line keeps the local secret scan that the bundled cross-cutting default ran before this file existed (claude-code-plugins plugins/toolchain/reference/ecosystems/cross-cutting.yaml:12, opt-in :18, met by the tracked .gitleaks.toml), so these records do not switch a secret scan off. Its command is that of ci-workflows' gitleaks composite, which this repository does not call (gitleaks/scan.sh with the defaults in gitleaks/action.yml); its version and checksum are that action.yml's `version` and `sha256` defaults. gitleaks scans every file on disk under the repository root, tracked, untracked or git-ignored (a scratch file under .work/ included), and not git history; it does not read <files>. No editorconfig-checker or markdownlint command: .editorconfig, .editorconfig-checker.json and .markdownlint-cli2.jsonc are standards-synced files that CI deliberately does not re-lint (pr-require-checks.yml:7-13; pr-check-managed-files-hosted.yml:41-42, :72), and no CI job here runs those tools; lefthook.yml:1-6 pulls git hooks from claude-code-plugins, and apart from gitleaks these records follow CI, not a local hook. Not run locally: the schema step of the validate-manifests job (pr-require-checks.yml:187-200); typescript.yaml gives the reason. Checks with no local form: the pull-request contract check (pr-require-checks.yml:303-306, check-contract at the commit it pins) and the result aggregation (:307-326, aggregate-results at the same commit) in the ci-status job (:281-283); they need the pull request. This ci-status job has no draft refusal. Not run locally: the model review lanes pr-review (.github/workflows/pr-review-hosted.yml:74-85) and pr-review-security (.github/workflows/pr-review-security-hosted.yml:67-78), which review the pull request through ci-workflows reusables called at @main, not pinned; both are advisory and skip drafts (pr-review-hosted.yml:37, :76-78; pr-review-security-hosted.yml:44-46, :69-71). Not run locally: check-managed-files (pr-check-managed-files-hosted.yml:106-127, check-managed-files@944d346 v0.74.0), which needs a melodic-software/standards checkout and the pull request; it is advisory and not aggregated into ci-status (:20-22). pr-automerge-dependabot (.github/workflows/pr-automerge-dependabot.yml:22-30) checks nothing; it arms auto-merge on a Dependabot pull request (:3-8)."
1 change: 0 additions & 1 deletion .claude/ecosystems/markdown.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,5 @@ fix-cmd: null
code-fix-cmd: null
opt-in: "always applies to plugins/*/skills/*/SKILL.md; the check needs no config"
install-hint: "None: the command uses only the shell and head."
tool-pin: {}
gates: []
notes: "check-cmd is CI's step with two changes: its result variable is fail, not status, which zsh holds read-only, and its last line is test in place of exit, so the command does not end the shell that runs it. It checks every plugins/*/skills/*/SKILL.md, not <files>, as CI does on every change. The glob expands on disk, so a local run also checks an untracked SKILL.md, which CI's clean checkout does not have. No markdownlint: without this file the bundled markdown default (claude-code-plugins plugins/toolchain/reference/ecosystems/markdown.yaml:7) would run markdownlint-cli2 on changed *.md files, because its opt-in, a markdownlint config (:9), is met by .markdownlint-cli2.jsonc; that file is standards-synced (.github/workflows/pr-check-managed-files-hosted.yml:72) and CI deliberately does not lint with it (pr-require-checks.yml:7-13). fix-cmd is null: CI has no markdown fix step. No job in this workflow has a path filter (:15-37), so CI runs this step on every change; the step reads only SKILL.md files, which these globs select."
1 change: 0 additions & 1 deletion .claude/ecosystems/powershell.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,5 @@ fix-cmd: null
code-fix-cmd: null
opt-in: "PSScriptAnalyzer always applies to scripts/sync-local.ps1; CI uses no settings file"
install-hint: "pwsh, then Install-Module PSScriptAnalyzer -Scope CurrentUser -Force, as CI runs it from PSGallery with no version pin (pr-require-checks.yml:132-136); CI verifies no checksum."
tool-pin: {}
gates: []
notes: "No tool-pin: CI installs the current PSGallery release of PSScriptAnalyzer (pr-require-checks.yml:136). check-cmd is CI's analyzer call (:149-154). It sets $ErrorActionPreference to Stop, which GitHub prepends to a shell: pwsh step (docs.github.com workflow syntax, 'Exit codes and error action preference') and a plain pwsh -Command does not: without it a missing PSScriptAnalyzer module leaves $findings empty and pwsh exits 0 after printing 0 findings. Deviation: the -SuppressedOnly listing (:144-148) only prints the deliberate suppressions and does not change the result, so it is left out. check-cmd analyzes CI's one path, not <files>, as CI does on every change; the repository holds no other PowerShell file. fix-cmd is null: CI has no format step. Glob gap: no job in this workflow has a path filter (:15-37), so CI runs the sync-local suite on every change; that suite runs this script beside its bash twin (scripts/test-sync-local.sh:4-6, :28) and is bash.yaml's test-cmd, so a change to only scripts/sync-local.ps1 runs no local test."
1 change: 0 additions & 1 deletion .claude/ecosystems/typescript.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,5 @@ check-cmd: null
fix-cmd: null
code-fix-cmd: null
install-hint: "None: this record runs no command."
tool-pin: {}
gates: []
notes: "Not run locally: CI's schema step (pr-require-checks.yml:187-200). It runs npm init -y and npm install ajv@8 ajv-formats in the repository root, which write package.json, package-lock.json and node_modules/ there, and curl writes marketplace.schema.json, plugin.schema.json and environment.schema.json there (:190-199), because the scripts read the schemas from the working directory (scripts/validate-manifests.mjs:13-15, scripts/validate-environment.mjs:9-10). .gitignore covers only node_modules/ of those (.gitignore:7), so a local run would leave a package.json, a package-lock.json and three schema files untracked in the tree. CI also fetches the schemas live from cursor/plugins main and cursor.com, and installs ajv@8 and ajv-formats with no exact version, so its result can change with no commit here. No opt-in key: there is no check-cmd for it to govern. Without this file the bundled typescript default (claude-code-plugins plugins/toolchain/reference/ecosystems/typescript.yaml:10, whose globs match *.mjs) would run its tsc, test and Biome commands (:12-14). The record is enabled: true with null commands rather than enabled: false: the repository holds JavaScript source, null commands read as not applicable, and false would also drop the lane for code-metrics, which reads enabled (the ecosystem-commands contract README, Consumers). The same job's jq step (:166-169) runs from cross-cutting.yaml and its skill-frontmatter step (:171-180) from markdown.yaml. Glob gap: no job in this workflow has a path filter (:15-37), so CI runs the schema step on every change; locally no record validates the manifests or .cursor/environment.json against Cursor's schemas, so a change to, for example, .cursor-plugin/marketplace.json, a plugins/*/.cursor-plugin/plugin.json or .cursor/environment.json gets only cross-cutting.yaml's jq syntax check, which does not read .cursor/environment.json."
1 change: 0 additions & 1 deletion .claude/ecosystems/yaml.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,5 @@ check-cmd: null
fix-cmd: null
code-fix-cmd: null
install-hint: "None: this record runs no command."
tool-pin: {}
gates: []
notes: "No command because CI has none for workflow lint. Without this file the bundled yaml default (claude-code-plugins plugins/toolchain/reference/ecosystems/yaml.yaml:8-11) would run actionlint, because its opt-in, GitHub Actions workflows present (:13), is met. The record is enabled: true with null commands rather than enabled: false: the repository holds workflows, null commands read as not applicable, and false would also drop the lane for code-metrics, which reads enabled (the ecosystem-commands contract README, Consumers). No opt-in key: there is no check-cmd for it to govern. The workflows' checks with no local form are listed in cross-cutting.yaml's notes. CI's typos lane spell-checks these files too (pr-require-checks.yml:272-276), and that check runs from cross-cutting.yaml."
Loading