[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77MD0YFDCE86Z1EGHGWM55N":3,"skill-same:01M77MD0YFDCE86Z1EGHGWM55N":66},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":49},"01M77MD0YFDCE86Z1EGHGWM55N","setup",null,"Verify and configure repo-fleet-hygiene for a consumer project. check inspects the optional .claude\u002Frepo-fleet-hygiene.conf read-only (presence, parse validity, path resolution); apply creates or updates it by adding bounded fleet roots, exact repositories, and remote-keyed canonical checkout overrides, preserving unrelated entries. Use when: 'set up repo fleet audit', 'is repo-fleet-hygiene configured', 'configure fleet roots', 'canonical repo override', 'dotfiles-manager checkout'. Re-runnable and safe.","melodic-software\u002Fclaude-code-plugins","melodic-software","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F58273638?v=4","01M77JVQTXNGKCE4MDFY2BC936","Melodic Software","01M77JVQVN9QDWKAH6W03ANP76",30,"MIT","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Frepo-fleet-hygiene\u002Fskills\u002Fsetup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Verify and configure repo-fleet-hygiene for a consumer project. check inspects the optional .claude\u002Frepo-fleet-hygiene.conf read-only (presence, parse validity, path resolution); apply creates or updates it by adding bounded fleet roots, exact repositories, and remote-keyed canonical checkout overrides, preserving unrelated entries. Use when: 'set up repo fleet audit', 'is repo-fleet-hygiene configured', 'configure fleet roots', 'canonical repo override', 'dotfiles-manager checkout'. Re-runnable and safe.\"\nuser-invocable: true\ndisable-model-invocation: true\nallowed-tools:\n  - Bash(${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fsetup-config.sh:*)\nargument-hint: \"[check|apply] [--config \u003Cpath>] [--root \u003Cdir>]... [--repo \u003Cdir>]... [--skip \u003Cname>]...\"\n---\n\n**Arguments.** `[check|apply] [--config \u003Cpath>] [--root \u003Cdir>]... [--repo \u003Cdir>]... [--skip \u003Cname>]...`. Full form: [check|apply] [--config \u003Cpath>] [--root \u003Cdir>]... [--repo \u003Cdir>]... [--canonical \u003Cgithub.com\u002Fowner\u002Frepo=path>]... [--ack-unavailable \u003Cgithub.com\u002Fowner\u002Frepo>]... [--skip \u003Cname>]... [--extend-skip \u003Cname>]... [--max-depth \u003C1..12>]\n\n## Purpose\n\nVerify and manage the audit's optional Git-format configuration. Setup owns only this file; it never\nedits Claude Code settings, `pluginConfigs`, Git remotes, branches, worktrees, or the installed plugin.\n\nThe config file itself is optional to *create*. A `\u002Frepo-fleet-hygiene:audit` takes scope from a\nCLI bare path \u002F `--root` \u002F `--repo`, or `fleet.root` \u002F `fleet.repo` entries in a consumed config.\nAbsence of every config on the ladder is therefore INFO for `check` (nothing to validate yet); a\nsubsequent no-argument audit then follows its no-scope ladder and exits 3 only when no rung\nresolves. Check-centric per the uniform setup contract\n(`docs\u002Fplugin-philosophy.md` \"Setup is explicit and repeatable\" in the marketplace repository):\n`check` inspects read-only; `apply` creates or updates the file, then re-runs `check`. No argument\nor `check` runs the check; `apply` runs the check first, then the write. All non-interactive: when\nthe arguments fully specify the change, `apply` proceeds without prompting.\n\nDefault config path: `${CLAUDE_PROJECT_DIR}\u002F.claude\u002Frepo-fleet-hygiene.conf`. An explicit `--config`\nmay choose another path. Resolve relative roots\u002Frepos\u002Fcanonical paths from the config file directory.\n\n**Scoping rule (state it in `check`\u002F`apply` output):** the audit consumes config through a ladder:\nexplicit `--config`, else the project-scoped default above, else the user-global\n`~\u002F.claude\u002Frepo-fleet-hygiene.conf`. A project-scoped config is therefore consumed only when the\naudit runs with that same project directory; a fleet config meant to apply from every project\nbelongs at the user-global path (`apply --config ~\u002F.claude\u002Frepo-fleet-hygiene.conf`). The audit\nreport header names which config (if any) was consumed.\n\n## Argument grammar\n\n```text\ncheck | apply [--config \u003Cpath>] [--root \u003Cdir>]... [--repo \u003Cdir>]...\n        [--canonical \u003Cgithub.com\u002Fowner\u002Frepo=path>]... [--ack-unavailable \u003Cgithub.com\u002Fowner\u002Frepo>]...\n        [--skip \u003Cname>]... [--extend-skip \u003Cname>]... [--max-depth \u003C1..12>]\n```\n\n`--max-depth` writes `[fleet] maxDepth`; `--skip` writes repeatable `[fleet] skip` entries;\n`--extend-skip` writes repeatable `[fleet] skipAppend` entries. This skill owns the config file\nthat carries them. See \"Configuration grammar\" below for the `skip` replace semantics, and state\nthem whenever you write a `skip` entry, because \"extend\" is the naive reading. An operator who\nwants to add names to the defaults wants `--extend-skip`.\n\n## `check` (read-only)\n\nThe config file and the grammar below are the source of truth. Probe, report a PASS\u002FFAIL\u002FINFO table\nwith one remediation line per FAIL, and modify nothing. Do NOT run the collector. That is\n`\u002Frepo-fleet-hygiene:audit`; `check` only validates the configuration the audit would consume, using\n`git config --file` and read-only filesystem probes.\n\n1. **Config presence**. Resolve the config path (`--config` or the default). Absent → INFO naming\n   the full ladder: the audit next probes the user-global `~\u002F.claude\u002Frepo-fleet-hygiene.conf` (report\n   whether one exists there); with no config on the ladder and no scope argument, a bare\n   `\u002Frepo-fleet-hygiene:audit` follows the no-scope ladder in that skill. `apply` scaffolds a\n   config only if the user wants bounded roots or overrides.\n2. **Parse validity**. Present config: `git config --file \"\u003Cpath>\" --list >\u002Fdev\u002Fnull`. A non-zero exit\n   is FAIL with the parse error in the remediation line. Never `source` the file.\n3. **Entry resolution**. For each `[fleet] root`\u002F`repo` and each `[canonical …] path`, resolve it from\n   the config directory and confirm the directory exists and (for roots\u002Frepos) `git rev-parse` succeeds\n   read-only. A referenced path that does not resolve is FAIL, naming the entry.\n4. **`maxDepth`**. Present and outside `1..12` is FAIL; absent is INFO (the audit's own default applies).\n5. **Canonical identity**. INFO for each `[canonical \"github.com\u002Fowner\u002Frepository\"]` entry: report the\n   normalized key. Flag as FAIL only a key that is not a normalizable `github.com\u002Fowner\u002Frepository`.\n6. **Acknowledged identities**. INFO listing each `fleet.ackUnavailable` entry (normalized). FAIL any\n   value that is not a normalizable `github.com\u002Fowner\u002Frepository`.\n7. **Discovery skip names**. INFO listing each `fleet.skip` and `fleet.skipAppend` entry. FAIL any\n   value that is empty or contains a path separator (must be a bare directory name). Remind that\n   any present `fleet.skip` **replaces** the audit default skip list rather than appending, while\n   `fleet.skipAppend` adds to whichever list is in effect.\n8. **Tracked-file pair** (only when the config lives inside a git worktree, e.g. a project's\n   tracked `.claude\u002Frepo-fleet-hygiene.conf`): resolve the worktree that owns the file\n   (`git -C \"$(dirname -- \"\u003Cpath>\")\" rev-parse --show-toplevel`) and run both probes there\n   with a path relative to that toplevel: `git -C \"\u003Ctoplevel>\" check-ignore -v -- \"\u003Crel>\"`\n   reports no match (a match is FAIL with the pattern, since teammates would never receive the\n   config) AND `git -C \"\u003Ctoplevel>\" ls-files --error-unmatch -- \"\u003Crel>\"` exits 0 (non-zero is\n   un-ignored but untracked; FAIL with \"commit it to share with the team\"). An explicit\n   `--config` in another checkout is still that other worktree's file; do not run the pair\n   against the current project's index. Skip both, saying so, when no owning worktree exists\n   (user-global `~\u002F.claude\u002F…` or any path outside a repository). A git verdict there is\n   meaningless.\n\n## `apply` (idempotent)\n\nRun `check`, then create or update the config from the supplied arguments.\n\n1. Parse only the declared argument grammar. Validate every root\u002Frepository\u002Fcanonical path with\n   read-only filesystem and `git rev-parse` checks. Normalize canonical keys to\n   `github.com\u002Fowner\u002Frepository` (lowercase host, case-preserving owner\u002Fname is acceptable).\n   Validate `--max-depth` as an integer in `1..12` and write it as `[fleet] maxDepth`; this skill\n   owns the file that carries it, so it must be settable here rather than by hand-editing.\n   Validate each `--ack-unavailable` value as a normalizable `github.com\u002Fowner\u002Frepository`\n   (no filesystem probe, the identity is expected to be inaccessible); write it as a repeatable\n   `[fleet] ackUnavailable` entry, deduplicating case-insensitively against entries already\n   present. Like roots\u002Frepos, apply is additive. Removing an acknowledgment is a manual edit of\n   the consumer's own config file.\n   Validate each `--skip` value as a bare directory name (reject empty and any path separator);\n   write it as a repeatable `[fleet] skip` entry, deduplicating exact matches against entries\n   already present. State the replace semantics from \"Configuration grammar\" when writing.\n   Validate each `--extend-skip` value the same way and write it as a repeatable\n   `[fleet] skipAppend` entry, deduplicating exact matches. Removing a skip entry is a manual edit.\n2. If the config exists, read it with `git config --file \u003Cpath> --list --show-origin`. Preserve every\n   unrelated entry. Never source it.\n3. State the proposed additions\u002Fupdates before writing. With complete arguments, proceed\n   non-interactively; otherwise ask only for the missing values. An empty invocation may create the\n   minimal current-project config:\n\n   ```gitconfig\n   [fleet]\n       repo = ..\n       maxDepth = 5\n   ```\n\n   (`..` is relative to `.claude\u002F` and therefore names `${CLAUDE_PROJECT_DIR}`.)\n4. Write `--root`, `--repo`, `--skip`, `--extend-skip`, and `--max-depth` by calling the bundled\n   script, never by hand-editing the file:\n\n   ```text\n   ${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fsetup-config.sh apply [--config \u003Cpath>] [--project-dir \u003Cdir>]\n       [--root \u003Cdir>]... [--repo \u003Cdir>]... [--skip \u003Cname>]... [--extend-skip \u003Cname>]... [--max-depth \u003Cn>]\n   ```\n\n   It validates the same rules as step 1, writes each entry with `git config --file \u003Cpath> --add`\n   after an exact-match check (a repeated run reports \"already configured\" and changes nothing),\n   preserves comments and unrelated entries, creates the parent directory, and refuses a symlink\n   target. It exits 2 on a validation error and writes nothing. Without `--config` it writes\n   `\u003Cproject-dir>\u002F.claude\u002Frepo-fleet-hygiene.conf` (`${CLAUDE_PROJECT_DIR}` when `--project-dir` is\n   absent). The script takes only those five options. For `--canonical` and `--ack-unavailable`,\n   which need the identity checks above, make an ordinary file edit so the user sees a deterministic\n   diff, preserving comments and unrelated sections.\n\n   The script writes each root and repository relative to the config file's directory, which the\n   grammar resolves identically and which passes the write-time path-portability guard some consumer\n   environments run on tracked config. Where no relative path exists (on Windows, two volumes: a\n   fleet root on `D:` with a config on `C:`) it writes the absolute path; say in the report that the\n   relative form was unavailable because the target is on another volume, so the guard's rejection\n   is not mistaken for a consumer error. Write any hand-edited `--canonical` path the same way.\n5. Verify after remediation. Re-run every `check` probe against the written file (never claim success on\n   the edit alone). Config-only, exactly as `check` defines them:\n\n   - **Parse validity**. `git config --file \"\u003Cconfig-path>\" --list >\u002Fdev\u002Fnull`\n   - **Entry resolution**. For each `[fleet] root`\u002F`repo` and each `[canonical …] path`, resolve from\n     the config directory and confirm the directory exists and (for roots\u002Frepos) `git rev-parse` succeeds\n     read-only\n   - **`maxDepth`**. When present, confirm it is an integer in `1..12`\n   - **Canonical identity** and **acknowledged identities**. Confirm each key\u002Fvalue normalizes to\n     `github.com\u002Fowner\u002Frepository`\n   - **Discovery skip names**. When present, confirm each `fleet.skip` and `fleet.skipAppend`\n     value is a bare directory name (non-empty, no path separator)\n   - **Tracked-file pair** (when the config lives inside a git worktree, e.g. the tracked\n     `.claude\u002Frepo-fleet-hygiene.conf`): resolve the owning worktree\n     (`git -C \"$(dirname -- \"\u003Cconfig-path>\")\" rev-parse --show-toplevel`) and run both probes\n     there with a toplevel-relative path: `git -C \"\u003Ctoplevel>\" check-ignore -v -- \"\u003Crel>\"`\n     reports no match (a match is FAIL with the pattern, since teammates would never receive the\n     config) AND `git -C \"\u003Ctoplevel>\" ls-files --error-unmatch -- \"\u003Crel>\"` exits 0 (non-zero\n     means un-ignored but still untracked, the guaranteed state right after a fresh write;\n     report \"written but untracked: commit it to share with the team\", never success). An\n     explicit `--config` in another checkout is still that other worktree's file. Skip both,\n     saying so, when no owning worktree exists. A git verdict there is meaningless.\n\n   Do **not** invoke the collector to verify a write. It is the full fleet walk this skill says it\n   never runs: per-repository network queries across every configured root, minutes on a real fleet,\n   and it proves nothing about the file that the `check` probes do not already prove. If the user\n   explicitly wants an end-to-end run, say that it is a real audit and hand off by invoking\n   `\u002Frepo-fleet-hygiene:audit` via the Skill tool.\n\n6. Report path, inferred\u002Fexplicit entries, preserved entries, and the config-verification result.\n\nRe-running `apply` with the same arguments after everything resolves changes nothing and reports\n\"already configured\".\n\n## Configuration grammar\n\n```gitconfig\n[fleet]\n    root = ..\u002F..\u002Frepos\u002Fgithub.com   # repeatable discovery root\n    repo = ..\u002F..\u002Fspecial\u002Frepo      # repeatable exact target\n    maxDepth = 5                   # integer 1..12\n    ackUnavailable = github.com\u002Fowner\u002Frepository   # repeatable; acknowledge a known-inaccessible identity\n    skip = vendor                  # repeatable; REPLACE default discovery skip list (not append)\n    skipAppend = third_party       # repeatable; ADD to whichever skip list is in effect\n\n[canonical \"github.com\u002Fowner\u002Frepository\"]\n    path = ..\u002F..\u002F..\u002Fcanonical-checkout\n```\n\n`ackUnavailable` demotes a 404\u002F403 `github-identity-unavailable` finding for that identity from\n`UNKNOWN` to `ACKNOWLEDGED` in the audit report, still reported, never suppressed, and never\naffecting non-404\u002F403 failures or successful-response evidence. Use it for foreseeable 404s:\nupstream repositories made private or deleted, or repositories owned by a different GitHub account\nthan the authenticated `gh` login.\n\n`skip` replaces the audit's default discovery skip list (`vendor` plus the package-manager cache\ntrees `node_modules`, `.venv`, `.pnpm-store`, `.yarn`, `.npm`, `.cargo`, `.rustup`, `.gradle`, `.m2`,\n`.nuget`, `__pycache__`, `.tox`) whenever any entry is present. It does **not** append. A lone\n`skip = third_party` means only `third_party` is skipped (plus unconditional `.` \u002F `..` \u002F `.git`).\nTo extend the defaults, write `skipAppend = third_party` instead: `skipAppend` (and the audit's\n`--extend-skip`) adds to whichever list is in effect, the defaults or an explicit `skip` list. CLI\n`--skip` and config `fleet.skip` compose additively with each other the same way other scope inputs\ndo; so do `--extend-skip` and `fleet.skipAppend`.\n\nResolution priority is explicit audit CLI override, canonical config entry, then the discovered\ncheckout's own **main worktree** (the first record of `git worktree list --porcelain`). A canonical\noverride is therefore not needed merely to steer the audit away from a linked worktree. The audit\nresolves that itself. Never add one because two directory names look similar; verify the normalized\nGitHub remote identity on both sides first.\n\n## What this skill does NOT do\n\n- Run a fleet audit. That is `\u002Frepo-fleet-hygiene:audit`. `check` validates config only; it never\n  walks the fleet.\n- Write the plugin cache, Claude Code user settings, or `pluginConfigs`. Nor any machine-local\n  state. The config is the consumer's own tracked file.\n- Touch Git remotes, branches, or worktrees.\n\n## Gotchas\n\n- **Absolute paths in tracked config can be rejected by consumer write guards.** A root, repository, or\n  canonical target written as an absolute path may trip a consumer's write-time path-portability guard;\n  the same target written relative to the config file's directory passes and resolves identically, so\n  `apply` prefers the relative form, except across Windows volumes, where no relative form exists and\n  the absolute path is the only honest option. When that happens, write the absolute path, say in the\n  report that no relative path exists between volumes, and name the consumer's remedies if the guard\n  still rejects the write: colocate the config with the fleet root on one volume, exempt this file or\n  path from the guard, or keep a user-global config outside the guard's scan. Do not fabricate a\n  relative path or leave the consumer to conclude they misconfigured something.\n- **A project-scoped config is consumed only from its own project.** Per the Scoping rule above, a\n  config meant to apply from every project belongs at the user-global\n  `~\u002F.claude\u002Frepo-fleet-hygiene.conf`, not a per-project path. Otherwise the audit silently narrows to\n  the project it was authored in. Two cases collapse this warning, and `check` should say which one\n  applies rather than repeating a caution that cannot bite: when the project directory *is* the home\n  directory both rungs name the same file, and when no project directory reaches the audit (the\n  session did not supply one) the project rung is unreachable outright, leaving the\n  user-global path the only one that can be consumed.\n- **Config-supplied scope is additive to the audit's CLI scope.** A configured root is walked even\n  when the audit is invoked with an explicit `--repo`, so a persisted fleet config widens every later\n  run. The audit's `Scope:` header line names each contributing rung; a consumed config cannot be\n  suppressed for a single run.\n","**Arguments.** `[check|apply] [--config \u003Cpath>] [--root \u003Cdir>]... [--repo \u003Cdir>]... [--skip \u003Cname>]...`. Full form: [check|apply] [--config \u003Cpath>] [--root \u003Cdir>]... [--repo \u003Cdir>]... [--canonical \u003Cgithub.com\u002Fowner\u002Frepo=path>]... [--ack-unavailable \u003Cgithub.com\u002Fowner\u002Frepo>]... [--skip \u003Cname>]... [--extend-skip \u003Cname>]... [--max-depth \u003C1..12>]\n\n## Purpose\n\nVerify and manage the audit's optional Git-format configuration. Setup owns only this file; it never\nedits Claude Code settings, `pluginConfigs`, Git remotes, branches, worktrees, or the installed plugin.\n\nThe config file itself is optional to *create*. A `\u002Frepo-fleet-hygiene:audit` takes scope from a\nCLI bare path \u002F `--root` \u002F `--repo`, or `fleet.root` \u002F `fleet.repo` entries in a consumed config.\nAbsence of every config on the ladder is therefore INFO for `check` (nothing to validate yet); a\nsubsequent no-argument audit then follows its no-scope ladder and exits 3 only when no rung\nresolves. Check-centric per the uniform setup contract\n(`docs\u002Fplugin-philosophy.md` \"Setup is explicit and repeatable\" in the marketplace repository):\n`check` inspects read-only; `apply` creates or updates the file, then re-runs `check`. No argument\nor `check` runs the check; `apply` runs the check first, then the write. All non-interactive: when\nthe arguments fully specify the change, `apply` proceeds without prompting.\n\nDefault config path: `${CLAUDE_PROJECT_DIR}\u002F.claude\u002Frepo-fleet-hygiene.conf`. An explicit `--config`\nmay choose another path. Resolve relative roots\u002Frepos\u002Fcanonical paths from the config file directory.\n\n**Scoping rule (state it in `check`\u002F`apply` output):** the audit consumes config through a ladder:\nexplicit `--config`, else the project-scoped default above, else the user-global\n`~\u002F.claude\u002Frepo-fleet-hygiene.conf`. A project-scoped config is therefore consumed only when the\naudit runs with that same project directory; a fleet config meant to apply from every project\nbelongs at the user-global path (`apply --config ~\u002F.claude\u002Frepo-fleet-hygiene.conf`). The audit\nreport header names which config (if any) was consumed.\n\n## Argument grammar\n\n```text\ncheck | apply [--config \u003Cpath>] [--root \u003Cdir>]... [--repo \u003Cdir>]...\n        [--canonical \u003Cgithub.com\u002Fowner\u002Frepo=path>]... [--ack-unavailable \u003Cgithub.com\u002Fowner\u002Frepo>]...\n        [--skip \u003Cname>]... [--extend-skip \u003Cname>]... [--max-depth \u003C1..12>]\n```\n\n`--max-depth` writes `[fleet] maxDepth`; `--skip` writes repeatable `[fleet] skip` entries;\n`--extend-skip` writes repeatable `[fleet] skipAppend` entries. This skill owns the config file\nthat carries them. See \"Configuration grammar\" below for the `skip` replace semantics, and state\nthem whenever you write a `skip` entry, because \"extend\" is the naive reading. An operator who\nwants to add names to the defaults wants `--extend-skip`.\n\n## `check` (read-only)\n\nThe config file and the grammar below are the source of truth. Probe, report a PASS\u002FFAIL\u002FINFO table\nwith one remediation line per FAIL, and modify nothing. Do NOT run the collector. That is\n`\u002Frepo-fleet-hygiene:audit`; `check` only validates the configuration the audit would consume, using\n`git config --file` and read-only filesystem probes.\n\n1. **Config presence**. Resolve the config path (`--config` or the default). Absent → INFO naming\n   the full ladder: the audit next probes the user-global `~\u002F.claude\u002Frepo-fleet-hygiene.conf` (report\n   whether one exists there); with no config on the ladder and no scope argument, a bare\n   `\u002Frepo-fleet-hygiene:audit` follows the no-scope ladder in that skill. `apply` scaffolds a\n   config only if the user wants bounded roots or overrides.\n2. **Parse validity**. Present config: `git config --file \"\u003Cpath>\" --list >\u002Fdev\u002Fnull`. A non-zero exit\n   is FAIL with the parse error in the remediation line. Never `source` the file.\n3. **Entry resolution**. For each `[fleet] root`\u002F`repo` and each `[canonical …] path`, resolve it from\n   the config directory and confirm the directory exists and (for roots\u002Frepos) `git rev-parse` succeeds\n   read-only. A referenced path that does not resolve is FAIL, naming the entry.\n4. **`maxDepth`**. Present and outside `1..12` is FAIL; absent is INFO (the audit's own default applies).\n5. **Canonical identity**. INFO for each `[canonical \"github.com\u002Fowner\u002Frepository\"]` entry: report the\n   normalized key. Flag as FAIL only a key that is not a normalizable `github.com\u002Fowner\u002Frepository`.\n6. **Acknowledged identities**. INFO listing each `fleet.ackUnavailable` entry (normalized). FAIL any\n   value that is not a normalizable `github.com\u002Fowner\u002Frepository`.\n7. **Discovery skip names**. INFO listing each `fleet.skip` and `fleet.skipAppend` entry. FAIL any\n   value that is empty or contains a path separator (must be a bare directory name). Remind that\n   any present `fleet.skip` **replaces** the audit default skip list rather than appending, while\n   `fleet.skipAppend` adds to whichever list is in effect.\n8. **Tracked-file pair** (only when the config lives inside a git worktree, e.g. a project's\n   tracked `.claude\u002Frepo-fleet-hygiene.conf`): resolve the worktree that owns the file\n   (`git -C \"$(dirname -- \"\u003Cpath>\")\" rev-parse --show-toplevel`) and run both probes there\n   with a path relative to that toplevel: `git -C \"\u003Ctoplevel>\" check-ignore -v -- \"\u003Crel>\"`\n   reports no match (a match is FAIL with the pattern, since teammates would never receive the\n   config) AND `git -C \"\u003Ctoplevel>\" ls-files --error-unmatch -- \"\u003Crel>\"` exits 0 (non-zero is\n   un-ignored but untracked; FAIL with \"commit it to share with the team\"). An explicit\n   `--config` in another checkout is still that other worktree's file; do not run the pair\n   against the current project's index. Skip both, saying so, when no owning worktree exists\n   (user-global `~\u002F.claude\u002F…` or any path outside a repository). A git verdict there is\n   meaningless.\n\n## `apply` (idempotent)\n\nRun `check`, then create or update the config from the supplied arguments.\n\n1. Parse only the declared argument grammar. Validate every root\u002Frepository\u002Fcanonical path with\n   read-only filesystem and `git rev-parse` checks. Normalize canonical keys to\n   `github.com\u002Fowner\u002Frepository` (lowercase host, case-preserving owner\u002Fname is acceptable).\n   Validate `--max-depth` as an integer in `1..12` and write it as `[fleet] maxDepth`; this skill\n   owns the file that carries it, so it must be settable here rather than by hand-editing.\n   Validate each `--ack-unavailable` value as a normalizable `github.com\u002Fowner\u002Frepository`\n   (no filesystem probe, the identity is expected to be inaccessible); write it as a repeatable\n   `[fleet] ackUnavailable` entry, deduplicating case-insensitively against entries already\n   present. Like roots\u002Frepos, apply is additive. Removing an acknowledgment is a manual edit of\n   the consumer's own config file.\n   Validate each `--skip` value as a bare directory name (reject empty and any path separator);\n   write it as a repeatable `[fleet] skip` entry, deduplicating exact matches against entries\n   already present. State the replace semantics from \"Configuration grammar\" when writing.\n   Validate each `--extend-skip` value the same way and write it as a repeatable\n   `[fleet] skipAppend` entry, deduplicating exact matches. Removing a skip entry is a manual edit.\n2. If the config exists, read it with `git config --file \u003Cpath> --list --show-origin`. Preserve every\n   unrelated entry. Never source it.\n3. State the proposed additions\u002Fupdates before writing. With complete arguments, proceed\n   non-interactively; otherwise ask only for the missing values. An empty invocation may create the\n   minimal current-project config:\n\n   ```gitconfig\n   [fleet]\n       repo = ..\n       maxDepth = 5\n   ```\n\n   (`..` is relative to `.claude\u002F` and therefore names `${CLAUDE_PROJECT_DIR}`.)\n4. Write `--root`, `--repo`, `--skip`, `--extend-skip`, and `--max-depth` by calling the bundled\n   script, never by hand-editing the file:\n\n   ```text\n   ${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fsetup-config.sh apply [--config \u003Cpath>] [--project-dir \u003Cdir>]\n       [--root \u003Cdir>]... [--repo \u003Cdir>]... [--skip \u003Cname>]... [--extend-skip \u003Cname>]... [--max-depth \u003Cn>]\n   ```\n\n   It validates the same rules as step 1, writes each entry with `git config --file \u003Cpath> --add`\n   after an exact-match check (a repeated run reports \"already configured\" and changes nothing),\n   preserves comments and unrelated entries, creates the parent directory, and refuses a symlink\n   target. It exits 2 on a validation error and writes nothing. Without `--config` it writes\n   `\u003Cproject-dir>\u002F.claude\u002Frepo-fleet-hygiene.conf` (`${CLAUDE_PROJECT_DIR}` when `--project-dir` is\n   absent). The script takes only those five options. For `--canonical` and `--ack-unavailable`,\n   which need the identity checks above, make an ordinary file edit so the user sees a deterministic\n   diff, preserving comments and unrelated sections.\n\n   The script writes each root and repository relative to the config file's directory, which the\n   grammar resolves identically and which passes the write-time path-portability guard some consumer\n   environments run on tracked config. Where no relative path exists (on Windows, two volumes: a\n   fleet root on `D:` with a config on `C:`) it writes the absolute path; say in the report that the\n   relative form was unavailable because the target is on another volume, so the guard's rejection\n   is not mistaken for a consumer error. Write any hand-edited `--canonical` path the same way.\n5. Verify after remediation. Re-run every `check` probe against the written file (never claim success on\n   the edit alone). Config-only, exactly as `check` defines them:\n\n   - **Parse validity**. `git config --file \"\u003Cconfig-path>\" --list >\u002Fdev\u002Fnull`\n   - **Entry resolution**. For each `[fleet] root`\u002F`repo` and each `[canonical …] path`, resolve from\n     the config directory and confirm the directory exists and (for roots\u002Frepos) `git rev-parse` succeeds\n     read-only\n   - **`maxDepth`**. When present, confirm it is an integer in `1..12`\n   - **Canonical identity** and **acknowledged identities**. Confirm each key\u002Fvalue normalizes to\n     `github.com\u002Fowner\u002Frepository`\n   - **Discovery skip names**. When present, confirm each `fleet.skip` and `fleet.skipAppend`\n     value is a bare directory name (non-empty, no path separator)\n   - **Tracked-file pair** (when the config lives inside a git worktree, e.g. the tracked\n     `.claude\u002Frepo-fleet-hygiene.conf`): resolve the owning worktree\n     (`git -C \"$(dirname -- \"\u003Cconfig-path>\")\" rev-parse --show-toplevel`) and run both probes\n     there with a toplevel-relative path: `git -C \"\u003Ctoplevel>\" check-ignore -v -- \"\u003Crel>\"`\n     reports no match (a match is FAIL with the pattern, since teammates would never receive the\n     config) AND `git -C \"\u003Ctoplevel>\" ls-files --error-unmatch -- \"\u003Crel>\"` exits 0 (non-zero\n     means un-ignored but still untracked, the guaranteed state right after a fresh write;\n     report \"written but untracked: commit it to share with the team\", never success). An\n     explicit `--config` in another checkout is still that other worktree's file. Skip both,\n     saying so, when no owning worktree exists. A git verdict there is meaningless.\n\n   Do **not** invoke the collector to verify a write. It is the full fleet walk this skill says it\n   never runs: per-repository network queries across every configured root, minutes on a real fleet,\n   and it proves nothing about the file that the `check` probes do not already prove. If the user\n   explicitly wants an end-to-end run, say that it is a real audit and hand off by invoking\n   `\u002Frepo-fleet-hygiene:audit` via the Skill tool.\n\n6. Report path, inferred\u002Fexplicit entries, preserved entries, and the config-verification result.\n\nRe-running `apply` with the same arguments after everything resolves changes nothing and reports\n\"already configured\".\n\n## Configuration grammar\n\n```gitconfig\n[fleet]\n    root = ..\u002F..\u002Frepos\u002Fgithub.com   # repeatable discovery root\n    repo = ..\u002F..\u002Fspecial\u002Frepo      # repeatable exact target\n    maxDepth = 5                   # integer 1..12\n    ackUnavailable = github.com\u002Fowner\u002Frepository   # repeatable; acknowledge a known-inaccessible identity\n    skip = vendor                  # repeatable; REPLACE default discovery skip list (not append)\n    skipAppend = third_party       # repeatable; ADD to whichever skip list is in effect\n\n[canonical \"github.com\u002Fowner\u002Frepository\"]\n    path = ..\u002F..\u002F..\u002Fcanonical-checkout\n```\n\n`ackUnavailable` demotes a 404\u002F403 `github-identity-unavailable` finding for that identity from\n`UNKNOWN` to `ACKNOWLEDGED` in the audit report, still reported, never suppressed, and never\naffecting non-404\u002F403 failures or successful-response evidence. Use it for foreseeable 404s:\nupstream repositories made private or deleted, or repositories owned by a different GitHub account\nthan the authenticated `gh` login.\n\n`skip` replaces the audit's default discovery skip list (`vendor` plus the package-manager cache\ntrees `node_modules`, `.venv`, `.pnpm-store`, `.yarn`, `.npm`, `.cargo`, `.rustup`, `.gradle`, `.m2`,\n`.nuget`, `__pycache__`, `.tox`) whenever any entry is present. It does **not** append. A lone\n`skip = third_party` means only `third_party` is skipped (plus unconditional `.` \u002F `..` \u002F `.git`).\nTo extend the defaults, write `skipAppend = third_party` instead: `skipAppend` (and the audit's\n`--extend-skip`) adds to whichever list is in effect, the defaults or an explicit `skip` list. CLI\n`--skip` and config `fleet.skip` compose additively with each other the same way other scope inputs\ndo; so do `--extend-skip` and `fleet.skipAppend`.\n\nResolution priority is explicit audit CLI override, canonical config entry, then the discovered\ncheckout's own **main worktree** (the first record of `git worktree list --porcelain`). A canonical\noverride is therefore not needed merely to steer the audit away from a linked worktree. The audit\nresolves that itself. Never add one because two directory names look similar; verify the normalized\nGitHub remote identity on both sides first.\n\n## What this skill does NOT do\n\n- Run a fleet audit. That is `\u002Frepo-fleet-hygiene:audit`. `check` validates config only; it never\n  walks the fleet.\n- Write the plugin cache, Claude Code user settings, or `pluginConfigs`. Nor any machine-local\n  state. The config is the consumer's own tracked file.\n- Touch Git remotes, branches, or worktrees.\n\n## Gotchas\n\n- **Absolute paths in tracked config can be rejected by consumer write guards.** A root, repository, or\n  canonical target written as an absolute path may trip a consumer's write-time path-portability guard;\n  the same target written relative to the config file's directory passes and resolves identically, so\n  `apply` prefers the relative form, except across Windows volumes, where no relative form exists and\n  the absolute path is the only honest option. When that happens, write the absolute path, say in the\n  report that no relative path exists between volumes, and name the consumer's remedies if the guard\n  still rejects the write: colocate the config with the fleet root on one volume, exempt this file or\n  path from the guard, or keep a user-global config outside the guard's scan. Do not fabricate a\n  relative path or leave the consumer to conclude they misconfigured something.\n- **A project-scoped config is consumed only from its own project.** Per the Scoping rule above, a\n  config meant to apply from every project belongs at the user-global\n  `~\u002F.claude\u002Frepo-fleet-hygiene.conf`, not a per-project path. Otherwise the audit silently narrows to\n  the project it was authored in. Two cases collapse this warning, and `check` should say which one\n  applies rather than repeating a caution that cannot bite: when the project directory *is* the home\n  directory both rungs name the same file, and when no project directory reaches the audit (the\n  session did not supply one) the project rung is unreachable outright, leaving the\n  user-global path the only one that can be consumed.\n- **Config-supplied scope is additive to the audit's CLI scope.** A configured root is walked even\n  when the audit is invoked with an explicit `--repo`, so a persisted fleet config widens every later\n  run. The audit's `Scope:` header line names each contributing rung; a consumed config cannot be\n  suppressed for a single run.\n",{"description":7,"allowed-tools":24,"argument-hint":26,"user-invocable":27,"disable-model-invocation":27},[25],"Bash(${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fsetup-config.sh:*)","[check|apply] [--config \u003Cpath>] [--root \u003Cdir>]... [--repo \u003Cdir>]... [--skip \u003Cname>]...",true,"main","d0e68c3f36b92a1d6381f0ba0060d7a0b8b886c5","plugins\u002Frepo-fleet-hygiene\u002Fskills\u002Fsetup",7,"https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins","https:\u002F\u002Fgithub.com\u002Fmelodic-software","https:\u002F\u002Fmelodicsoftware.com","Independent software studio building developer tools, automation, and application services, with roots in music.","2026-11-15 05:15:06",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":27},[39,42,45],{"tool":40,"command":41},"npx","npx skills add melodic-software\u002Fclaude-code-plugins --skill setup",{"tool":43,"command":44},"bunx","bunx skills add melodic-software\u002Fclaude-code-plugins --skill setup",{"tool":46,"command":47},"pnpm","pnpm dlx skills add melodic-software\u002Fclaude-code-plugins --skill setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Frepo-fleet-hygiene\u002Fskills\u002Fsetup\u002FSKILL.md",[50,56,62],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"evals\u002Fevals.json","REFERENCE","参考文档",6380,"https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Frepo-fleet-hygiene\u002Fskills\u002Fsetup\u002Fevals\u002Fevals.json",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"scripts\u002Fsetup-config.sh","SCRIPT","脚本",4396,"https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Frepo-fleet-hygiene\u002Fskills\u002Fsetup\u002Fscripts\u002Fsetup-config.sh",{"path":63,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":64,"sourceHtmlUrl":65},"scripts\u002Fsetup-config.test.sh",4289,"https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Frepo-fleet-hygiene\u002Fskills\u002Fsetup\u002Fscripts\u002Fsetup-config.test.sh",[67,74,81,88,93,100],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7DYYDG31B9YX7N9MB9QW2GW","track","Backlog reads through the bound tracker: search open and closed items, view one item with its comments and state history. Use when another skill searches or reads tracker items.","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsession-flow\u002Fevals\u002Frecall-still-reports-reopened-bug\u002Fwork-items-stub\u002Fskills\u002Ftrack\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7DYXVBAVG3NV30PA7GKW9Q6","reviewer-media","Reviewer media for one pull request: decides whether it needs a narrated walkthrough, builds the storyboard from \u002Freview:explain-change's digest, has \u002Fexplainer-video:produce render it and hands the manifest to \u002Fsource-control:pull-request media. Use when asked for 'reviewer media', 'a walkthrough video for this PR', 'a produced video of this change', or when pull-request ready or monitor hands a PR over.","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freview\u002Fskills\u002Freviewer-media\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7DYRZ5YD44AMYH26YR25GZ8","route","Model and effort per agent role (orchestrator, worker, verifier, retrieval) for a multi-agent run, resolved through the bundled defaults and the user, team and personal override config layers into fenced JSON with single-agent and fan-out variants and the layer behind each value. Use when asked 'which model for the subagents', 'route the roles' or 'model routing', or before a skill passes a role's model on a spawn.","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fdiscovery\u002Fevals\u002Fex-model-pin-without-override\u002Fmulti-agent-stub\u002Fskills\u002Froute\u002FSKILL.md",[],[],{"skillNo":89,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7DYRTVT4FWTGDJY0HCCFJMZ","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fdiscovery\u002Fevals\u002Fex-model-override-from-route\u002Fmulti-agent-stub\u002Fskills\u002Froute\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7DYNZC8PNW3T27V2ADKECKJ","principles","Module-design vocabulary for architecture findings, and the checks built on it. Use when: 'what is a deep module', 'what is a seam', 'deep vs shallow module', 'what is the deletion test', 'leverage and locality', 'module design vocabulary', 'which word do we use for X in architecture findings'. Scanning a codebase for friction is \u002Farchitecture:improve.","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Farchitecture\u002Fskills\u002Fprinciples\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7DYNMCZNEWBFHV9KTSS6H60","write","Structured five-field bug report (title, steps to reproduce, expected vs actual, justified severity, suggested fix location) from an informal description, read-only. Use when the user names a defect they observed, or asks for one written up ('report a bug', 'file a bug', 'write this up as a bug').","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Farchitecture\u002Fevals\u002Fdeepening-defect-goes-to-bugs-write\u002Fbugs-stub\u002Fskills\u002Fwrite\u002FSKILL.md",[],[]]