[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77MVJSTQXAMD24V8RZKWM3W":3,"skill-same:01M77MVJSTQXAMD24V8RZKWM3W":58},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":47},"01M77MVJSTQXAMD24V8RZKWM3W","setup",null,"Configure the testing plugin's can't-fail checks for this repository. check prints the resolved testing config cascade, which test-lint rules the repo's lint config turns on per language (a missing one is a finding), an optional instruction line to paste, and any test glob the shipped test-weaken hook skips; apply writes your answers to docs\u002Fconventions\u002Ftesting.yaml (or to the docs\u002Fconventions\u002Ftesting.md block or .claude\u002Ftesting.yaml when that is the team file in use). Use when: 'set up testing', 'configure the test scan', 'exclude these tests from the audit', 'add a test glob', 'which test lint rules are missing', 'testing setup'. Re-runnable.","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\u002Ftesting\u002Fskills\u002Fsetup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Configure the testing plugin's can't-fail checks for this repository. check prints the resolved testing config cascade, which test-lint rules the repo's lint config turns on per language (a missing one is a finding), an optional instruction line to paste, and any test glob the shipped test-weaken hook skips; apply writes your answers to docs\u002Fconventions\u002Ftesting.yaml (or to the docs\u002Fconventions\u002Ftesting.md block or .claude\u002Ftesting.yaml when that is the team file in use). Use when: 'set up testing', 'configure the test scan', 'exclude these tests from the audit', 'add a test glob', 'which test lint rules are missing', 'testing setup'. Re-runnable.\"\nargument-hint: \"[check|apply]\"\nuser-invocable: true\ndisable-model-invocation: true\n---\n\n## Purpose\n\n`\u002Ftesting:audit` and the opt-in `test-weaken` hook find tests by the shipped adapters' filename globs\nand judge them by the shipped rule levels. This skill shows what a repository changed about that\nthrough the testing config, and writes it. `check` changes nothing; `apply` runs `check`,\nasks, writes, and runs `check` again. No argument means `check`.\n\nIt never edits `CLAUDE.md` or `AGENTS.md`. The instruction line is printed for you to paste.\n\n## The config\n\nThe testing config resolves across the config-cascade layers, in order: `~\u002F.claude\u002Ftesting.yaml`,\nthe team layer and `\u003Croot>\u002F.claude\u002Ftesting.local.yaml`, where `\u003Croot>` is the scanned file's git\ntoplevel, else `${CLAUDE_PROJECT_DIR}`. The team layer is `\u003Croot>\u002Fdocs\u002Fconventions\u002Ftesting.yaml`.\nWithout it, the team layer is the `yaml config` block in `\u003Croot>\u002Fdocs\u002Fconventions\u002Ftesting.md`\n(read for one more release), else `\u003Croot>\u002F.claude\u002Ftesting.yaml`; the first present wins and the\nresolver prints a warning naming each one it ignores. Lists concatenate across layers; a later\nlayer's scalar overrides. The format is the adapters' YAML subset in every file; a glob that starts\nwith `*` must be single-quoted. `docs\u002Fconventions\u002Ftesting.yaml` also holds `\u002Ftesting:run-e2e`'s\n`e2e_driver`, `reuse_running_instance` and `browser_driver`, and `\u002Ftesting:write`'s\n`tdd_refactor_step` and `first_test`, which the scan ignores.\n\nThe keys:\n\n```yaml\nadapters:\n  disable: [py-unittest]         # wins over enable; a non-empty enable list is an allowlist\npaths:\n  exclude: ['legacy\u002F**']         # relative to the repo root; ** crosses \u002F, * does not\n  include: ['build\u002F**\u002F*.test.ts'] # reaches pruned folders; an adapter must still claim the file\nadapter_dirs: [tools\u002Ftest-adapters]  # consumer adapters, same schema as the shipped ones\nextend:\n  js-vitest:\n    files: ['*.it.ts']           # appended to that adapter's list field\nrules:\n  rule-weak-oracle: off          # off drops, warn reports without gating, error gates --check\n  test-weaken-block: error       # test-weaken hook: deny an added skip or a removed test\n```\n\nThe opt-in `test-weaken` hook runs before a Write or Edit to a test file and names what it removes:\ntest blocks, assertions, a changed expected value, or an added skip. By default it only tells the\nagent. With `test-weaken-block: error`, an added skip or a removed test block is\ndenied until the edit carries a `test-change: \u003Creason>` comment; removed assertions and changed\nexpected values are never denied. The agent can write that marker itself: it makes the reason\nvisible to reviewers, it does not prove the reason.\n\nRemovals (`adapters.disable`, `paths.exclude`, `rules ... off`) apply inside the scanner, so the\naudit goes quiet with no plugin change; an excluded path or a disabled adapter silences\n`test-weaken` too. Additions reach the audit at once; `test-weaken` covers only the shipped globs.\n\n## The test judge\n\nThe judge that asks where each changed test's expected value came from runs on demand, as\n`\u002Ftesting:audit --judge`, and in `\u002Fsource-control:pull-request` prep. It has no plugin option and\nno hook.\n\n## `check` (read-only)\n\nRun the script and show its output as it prints:\n\n```bash\nbash \"${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fsetup\u002Fscripts\u002Fsetup.sh\" check\n```\n\nIt exits 0 with no finding, 1 when a test-lint rule is missing, 2 when a layer does not resolve\n(the file and line are on stderr). Its four sections:\n\n1. **config**: the resolved records, or the note that no layer exists.\n2. **lint**: one row per rule for each language the repository's tracked test files use. The script\n   reads the lint config as text: a rule named there, or its plugin referenced beside a recommended\n   config, reads as present. Treat a `PRESENT` row from the recommended-config path as likely rather\n   than proven, and say so. A `FINDING` is a gap to report, not a neutral absence. The rules:\n   - JS\u002FTS: `jest\u002Fvalid-expect` (eslint-plugin-jest), `vitest\u002Fvalid-expect` (`@vitest\u002Feslint-plugin`),\n     `playwright\u002Fmissing-playwright-await` and `playwright\u002Fno-focused-test` (eslint-plugin-playwright).\n     Which config each sits in is its rule page's to state:\n     [jest\u002Fvalid-expect](https:\u002F\u002Fgithub.com\u002Fjest-community\u002Feslint-plugin-jest\u002Fblob\u002Fmain\u002Fdocs\u002Frules\u002Fvalid-expect.md),\n     [vitest\u002Fvalid-expect](https:\u002F\u002Fgithub.com\u002Fvitest-dev\u002Feslint-plugin-vitest\u002Fblob\u002Fmain\u002Fdocs\u002Frules\u002Fvalid-expect.md),\n     [playwright\u002Fmissing-playwright-await](https:\u002F\u002Fgithub.com\u002Fplaywright-community\u002Feslint-plugin-playwright\u002Fblob\u002Fmain\u002Fdocs\u002Frules\u002Fmissing-playwright-await.md),\n     [playwright\u002Fno-focused-test](https:\u002F\u002Fgithub.com\u002Fplaywright-community\u002Feslint-plugin-playwright\u002Fblob\u002Fmain\u002Fdocs\u002Frules\u002Fno-focused-test.md).\n     As of 2026-11-10; recheck when a plugin release note moves one of these rules out of its\n     recommended config or renames it.\n   - C#: `xUnit2021` (xunit.analyzers, which the check counts as present through an `xunit` or\n     `xunit.v3` reference) and `NUnit2009` (NUnit.Analyzers, which the check requires as its own\n     reference). Packaging: [xUnit2021](https:\u002F\u002Fxunit.net\u002Fxunit.analyzers\u002Frules\u002FxUnit2021) and\n     [NUnit2009](https:\u002F\u002Fdocs.nunit.org\u002Farticles\u002Fnunit-analyzers\u002FNUnit2009.html). As of 2026-11-10;\n     recheck when an xunit or NUnit release note changes how the analyzers are packaged.\n   - Python: ruff `PLR0124`, `PT011` and `F631`. The check counts `PLR0124` and `F631` as on with no\n     `select`, `PT011` as off, and a `select` as replacing the defaults with prefix matching\n     (`setup.sh` `ruff_rule`). Pointer: [ruff settings § lint.select](https:\u002F\u002Fdocs.astral.sh\u002Fruff\u002Fsettings\u002F#lint_select)\n     and the rule pages for [PLR0124](https:\u002F\u002Fdocs.astral.sh\u002Fruff\u002Frules\u002Fcomparison-with-itself\u002F),\n     [PT011](https:\u002F\u002Fdocs.astral.sh\u002Fruff\u002Frules\u002Fpytest-raises-too-broad\u002F) and\n     [F631](https:\u002F\u002Fdocs.astral.sh\u002Fruff\u002Frules\u002Fassert-tuple\u002F). As of 2026-11-10; recheck when a ruff\n     release note changes the default rule set.\n   - Bash, PowerShell and Go: no maintained rule.\n   - Any other detected language: named with `setup has no lint check for this language`, not a\n     finding.\n3. **instruction**: the optional line, naming the one file Claude Code loads at the repository\n   root: `CLAUDE.md`, else `.claude\u002FCLAUDE.md`, else `CLAUDE.local.md`, else `AGENTS.md`, else `CLAUDE.md` in\n   `${CLAUDE_CONFIG_DIR:-~\u002F.claude}` (the script's order). Which files load, and when `AGENTS.md` is\n   read: [memory § When Claude Code reads AGENTS.md](https:\u002F\u002Fcode.claude.com\u002Fdocs\u002Fen\u002Fmemory#when-claude-code-reads-agents-md). Offer it; do not paste it anywhere.\n4. **hook-entry**: a `none:` line saying test-quality findings come from `\u002Ftesting:audit`, not a\n   per-edit hook, then, when a consumer glob matches no shipped `test-weaken` row, a line naming\n   those globs: the audit scans them, `test-weaken` skips them. No settings entry is printed.\n\nThen probe the hook launcher, which the script does not: run `command -v node` via Bash and report\n`node` as a FAIL row when it is absent. Every hook row launches through `node hooks\u002Fexec-bash.mjs`,\nso a missing `node` is a hook launch error, not a skip notice, and a hook cannot report its own\nmissing launcher.\n\n## `apply`\n\n1. Run `check` and summarize the effective config before proposing a change. Nothing already\n   configured is dropped without the user confirming.\n2. Ask only what the repository cannot answer: folders or files to leave out, test files the\n   shipped globs miss (and which adapter reads them), adapters to turn off, rule levels.\n3. Write the team layer with the answers. The script writes the team file in use:\n   `docs\u002Fconventions\u002Ftesting.yaml` whole (keeping its `e2e_driver`, `reuse_running_instance`, `browser_driver`,\n   `tdd_refactor_step` and `first_test` lines), else the body of the `yaml config` block in `docs\u002Fconventions\u002Ftesting.md` (the rest of\n   that file stays), else `.claude\u002Ftesting.yaml` whole; with none, it creates\n   `docs\u002Fconventions\u002Ftesting.yaml`. It keeps the result only when it resolves and writes nothing\n   else; pass every value the team layer should hold, the existing ones included:\n\n   ```bash\n   bash \"${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fsetup\u002Fscripts\u002Fsetup.sh\" apply \\\n     --exclude 'legacy\u002F**' --extend js-vitest.files='*.it.ts' --rule weak-oracle=warn\n   ```\n\n   Flags: `--include`, `--exclude`, `--enable`, `--disable`, `--adapter-dir`,\n   `--extend \u003Cid>.\u003Cfield>=\u003Cvalue>`, `--rule \u003Crule>=off|warn|error`, each repeatable.\n4. Run `check` again. Offer `git add` for the file\n   `apply` printed and a commit, and run each only when the user accepts. Personal overrides go in\n   `.claude\u002Ftesting.local.yaml`, which should be gitignored. `check` also prints the optional line\n   to paste into `CLAUDE.md` or `AGENTS.md` that points at `docs\u002Fconventions\u002Ftesting.md` when that\n   file exists.\n\n## Next\n\n\u002Ftesting:audit\nRuns the scan with the config this skill wrote.\n\n## What this skill does NOT do\n\n- Edit `CLAUDE.md`, `AGENTS.md`, `.claude\u002Fsettings.json`, or any lint config. It prints what to add.\n- Install a lint plugin or analyzer.\n- Run the audit. That is `\u002Ftesting:audit`.\n","## Purpose\n\n`\u002Ftesting:audit` and the opt-in `test-weaken` hook find tests by the shipped adapters' filename globs\nand judge them by the shipped rule levels. This skill shows what a repository changed about that\nthrough the testing config, and writes it. `check` changes nothing; `apply` runs `check`,\nasks, writes, and runs `check` again. No argument means `check`.\n\nIt never edits `CLAUDE.md` or `AGENTS.md`. The instruction line is printed for you to paste.\n\n## The config\n\nThe testing config resolves across the config-cascade layers, in order: `~\u002F.claude\u002Ftesting.yaml`,\nthe team layer and `\u003Croot>\u002F.claude\u002Ftesting.local.yaml`, where `\u003Croot>` is the scanned file's git\ntoplevel, else `${CLAUDE_PROJECT_DIR}`. The team layer is `\u003Croot>\u002Fdocs\u002Fconventions\u002Ftesting.yaml`.\nWithout it, the team layer is the `yaml config` block in `\u003Croot>\u002Fdocs\u002Fconventions\u002Ftesting.md`\n(read for one more release), else `\u003Croot>\u002F.claude\u002Ftesting.yaml`; the first present wins and the\nresolver prints a warning naming each one it ignores. Lists concatenate across layers; a later\nlayer's scalar overrides. The format is the adapters' YAML subset in every file; a glob that starts\nwith `*` must be single-quoted. `docs\u002Fconventions\u002Ftesting.yaml` also holds `\u002Ftesting:run-e2e`'s\n`e2e_driver`, `reuse_running_instance` and `browser_driver`, and `\u002Ftesting:write`'s\n`tdd_refactor_step` and `first_test`, which the scan ignores.\n\nThe keys:\n\n```yaml\nadapters:\n  disable: [py-unittest]         # wins over enable; a non-empty enable list is an allowlist\npaths:\n  exclude: ['legacy\u002F**']         # relative to the repo root; ** crosses \u002F, * does not\n  include: ['build\u002F**\u002F*.test.ts'] # reaches pruned folders; an adapter must still claim the file\nadapter_dirs: [tools\u002Ftest-adapters]  # consumer adapters, same schema as the shipped ones\nextend:\n  js-vitest:\n    files: ['*.it.ts']           # appended to that adapter's list field\nrules:\n  rule-weak-oracle: off          # off drops, warn reports without gating, error gates --check\n  test-weaken-block: error       # test-weaken hook: deny an added skip or a removed test\n```\n\nThe opt-in `test-weaken` hook runs before a Write or Edit to a test file and names what it removes:\ntest blocks, assertions, a changed expected value, or an added skip. By default it only tells the\nagent. With `test-weaken-block: error`, an added skip or a removed test block is\ndenied until the edit carries a `test-change: \u003Creason>` comment; removed assertions and changed\nexpected values are never denied. The agent can write that marker itself: it makes the reason\nvisible to reviewers, it does not prove the reason.\n\nRemovals (`adapters.disable`, `paths.exclude`, `rules ... off`) apply inside the scanner, so the\naudit goes quiet with no plugin change; an excluded path or a disabled adapter silences\n`test-weaken` too. Additions reach the audit at once; `test-weaken` covers only the shipped globs.\n\n## The test judge\n\nThe judge that asks where each changed test's expected value came from runs on demand, as\n`\u002Ftesting:audit --judge`, and in `\u002Fsource-control:pull-request` prep. It has no plugin option and\nno hook.\n\n## `check` (read-only)\n\nRun the script and show its output as it prints:\n\n```bash\nbash \"${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fsetup\u002Fscripts\u002Fsetup.sh\" check\n```\n\nIt exits 0 with no finding, 1 when a test-lint rule is missing, 2 when a layer does not resolve\n(the file and line are on stderr). Its four sections:\n\n1. **config**: the resolved records, or the note that no layer exists.\n2. **lint**: one row per rule for each language the repository's tracked test files use. The script\n   reads the lint config as text: a rule named there, or its plugin referenced beside a recommended\n   config, reads as present. Treat a `PRESENT` row from the recommended-config path as likely rather\n   than proven, and say so. A `FINDING` is a gap to report, not a neutral absence. The rules:\n   - JS\u002FTS: `jest\u002Fvalid-expect` (eslint-plugin-jest), `vitest\u002Fvalid-expect` (`@vitest\u002Feslint-plugin`),\n     `playwright\u002Fmissing-playwright-await` and `playwright\u002Fno-focused-test` (eslint-plugin-playwright).\n     Which config each sits in is its rule page's to state:\n     [jest\u002Fvalid-expect](https:\u002F\u002Fgithub.com\u002Fjest-community\u002Feslint-plugin-jest\u002Fblob\u002Fmain\u002Fdocs\u002Frules\u002Fvalid-expect.md),\n     [vitest\u002Fvalid-expect](https:\u002F\u002Fgithub.com\u002Fvitest-dev\u002Feslint-plugin-vitest\u002Fblob\u002Fmain\u002Fdocs\u002Frules\u002Fvalid-expect.md),\n     [playwright\u002Fmissing-playwright-await](https:\u002F\u002Fgithub.com\u002Fplaywright-community\u002Feslint-plugin-playwright\u002Fblob\u002Fmain\u002Fdocs\u002Frules\u002Fmissing-playwright-await.md),\n     [playwright\u002Fno-focused-test](https:\u002F\u002Fgithub.com\u002Fplaywright-community\u002Feslint-plugin-playwright\u002Fblob\u002Fmain\u002Fdocs\u002Frules\u002Fno-focused-test.md).\n     As of 2026-11-10; recheck when a plugin release note moves one of these rules out of its\n     recommended config or renames it.\n   - C#: `xUnit2021` (xunit.analyzers, which the check counts as present through an `xunit` or\n     `xunit.v3` reference) and `NUnit2009` (NUnit.Analyzers, which the check requires as its own\n     reference). Packaging: [xUnit2021](https:\u002F\u002Fxunit.net\u002Fxunit.analyzers\u002Frules\u002FxUnit2021) and\n     [NUnit2009](https:\u002F\u002Fdocs.nunit.org\u002Farticles\u002Fnunit-analyzers\u002FNUnit2009.html). As of 2026-11-10;\n     recheck when an xunit or NUnit release note changes how the analyzers are packaged.\n   - Python: ruff `PLR0124`, `PT011` and `F631`. The check counts `PLR0124` and `F631` as on with no\n     `select`, `PT011` as off, and a `select` as replacing the defaults with prefix matching\n     (`setup.sh` `ruff_rule`). Pointer: [ruff settings § lint.select](https:\u002F\u002Fdocs.astral.sh\u002Fruff\u002Fsettings\u002F#lint_select)\n     and the rule pages for [PLR0124](https:\u002F\u002Fdocs.astral.sh\u002Fruff\u002Frules\u002Fcomparison-with-itself\u002F),\n     [PT011](https:\u002F\u002Fdocs.astral.sh\u002Fruff\u002Frules\u002Fpytest-raises-too-broad\u002F) and\n     [F631](https:\u002F\u002Fdocs.astral.sh\u002Fruff\u002Frules\u002Fassert-tuple\u002F). As of 2026-11-10; recheck when a ruff\n     release note changes the default rule set.\n   - Bash, PowerShell and Go: no maintained rule.\n   - Any other detected language: named with `setup has no lint check for this language`, not a\n     finding.\n3. **instruction**: the optional line, naming the one file Claude Code loads at the repository\n   root: `CLAUDE.md`, else `.claude\u002FCLAUDE.md`, else `CLAUDE.local.md`, else `AGENTS.md`, else `CLAUDE.md` in\n   `${CLAUDE_CONFIG_DIR:-~\u002F.claude}` (the script's order). Which files load, and when `AGENTS.md` is\n   read: [memory § When Claude Code reads AGENTS.md](https:\u002F\u002Fcode.claude.com\u002Fdocs\u002Fen\u002Fmemory#when-claude-code-reads-agents-md). Offer it; do not paste it anywhere.\n4. **hook-entry**: a `none:` line saying test-quality findings come from `\u002Ftesting:audit`, not a\n   per-edit hook, then, when a consumer glob matches no shipped `test-weaken` row, a line naming\n   those globs: the audit scans them, `test-weaken` skips them. No settings entry is printed.\n\nThen probe the hook launcher, which the script does not: run `command -v node` via Bash and report\n`node` as a FAIL row when it is absent. Every hook row launches through `node hooks\u002Fexec-bash.mjs`,\nso a missing `node` is a hook launch error, not a skip notice, and a hook cannot report its own\nmissing launcher.\n\n## `apply`\n\n1. Run `check` and summarize the effective config before proposing a change. Nothing already\n   configured is dropped without the user confirming.\n2. Ask only what the repository cannot answer: folders or files to leave out, test files the\n   shipped globs miss (and which adapter reads them), adapters to turn off, rule levels.\n3. Write the team layer with the answers. The script writes the team file in use:\n   `docs\u002Fconventions\u002Ftesting.yaml` whole (keeping its `e2e_driver`, `reuse_running_instance`, `browser_driver`,\n   `tdd_refactor_step` and `first_test` lines), else the body of the `yaml config` block in `docs\u002Fconventions\u002Ftesting.md` (the rest of\n   that file stays), else `.claude\u002Ftesting.yaml` whole; with none, it creates\n   `docs\u002Fconventions\u002Ftesting.yaml`. It keeps the result only when it resolves and writes nothing\n   else; pass every value the team layer should hold, the existing ones included:\n\n   ```bash\n   bash \"${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fsetup\u002Fscripts\u002Fsetup.sh\" apply \\\n     --exclude 'legacy\u002F**' --extend js-vitest.files='*.it.ts' --rule weak-oracle=warn\n   ```\n\n   Flags: `--include`, `--exclude`, `--enable`, `--disable`, `--adapter-dir`,\n   `--extend \u003Cid>.\u003Cfield>=\u003Cvalue>`, `--rule \u003Crule>=off|warn|error`, each repeatable.\n4. Run `check` again. Offer `git add` for the file\n   `apply` printed and a commit, and run each only when the user accepts. Personal overrides go in\n   `.claude\u002Ftesting.local.yaml`, which should be gitignored. `check` also prints the optional line\n   to paste into `CLAUDE.md` or `AGENTS.md` that points at `docs\u002Fconventions\u002Ftesting.md` when that\n   file exists.\n\n## Next\n\n\u002Ftesting:audit\nRuns the scan with the config this skill wrote.\n\n## What this skill does NOT do\n\n- Edit `CLAUDE.md`, `AGENTS.md`, `.claude\u002Fsettings.json`, or any lint config. It prints what to add.\n- Install a lint plugin or analyzer.\n- Run the audit. That is `\u002Ftesting:audit`.\n",{"description":7,"argument-hint":24,"user-invocable":25,"disable-model-invocation":25},"[check|apply]",true,"main","4f2dcaaff35e8f9fccc6a9f4d82a5830ab17a5c5","plugins\u002Ftesting\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":36,"prompt":46,"zipAvailable":25},[37,40,43],{"tool":38,"command":39},"npx","npx skills add melodic-software\u002Fclaude-code-plugins --skill setup",{"tool":41,"command":42},"bunx","bunx skills add melodic-software\u002Fclaude-code-plugins --skill setup",{"tool":44,"command":45},"pnpm","pnpm dlx skills add melodic-software\u002Fclaude-code-plugins --skill setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftesting\u002Fskills\u002Fsetup\u002FSKILL.md",[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"scripts\u002Fsetup.sh","SCRIPT","脚本",16636,"https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftesting\u002Fskills\u002Fsetup\u002Fscripts\u002Fsetup.sh",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"scripts\u002Fsetup.test.sh",17491,"https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftesting\u002Fskills\u002Fsetup\u002Fscripts\u002Fsetup.test.sh",[59,66,73,80,85,92],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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":81,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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",[],[]]