[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7546HS7HPRZTXEVRYV2XQKZ":3,"skill-same:01M7546HS7HPRZTXEVRYV2XQKZ":84},{"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":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":43,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M7546HS7HPRZTXEVRYV2XQKZ","release-changelog-harness",null,"For Changesets\u002FMelos\u002Frelease-plz, CHANGELOG hygiene, release CI, install.sh, and binary\u002FGitHub Release distribution for CLIs and meta skill marketplaces. Not for repo quality baselines, ADRs, harness dogfood, or domain app feature work—use repo-quality-system-lifecycle or native product gates.","Arenukvern\u002Fskill_steward","Arenukvern","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F15068151?v=4","01M754581MP48JSE9S108XFZF4","Anton Malofeev","01M754582P7BZHZ5F3RXDKEP1D",13,"MIT","https:\u002F\u002Fgithub.com\u002FArenukvern\u002Fskill_steward\u002Fblob\u002Fmain\u002Fskills\u002Frelease-changelog-harness\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: release-changelog-harness\ndescription: >-\n  For Changesets\u002FMelos\u002Frelease-plz, CHANGELOG hygiene, release CI, install.sh, and binary\u002FGitHub Release distribution for CLIs and meta skill marketplaces.\n  Not for repo quality baselines, ADRs, harness dogfood, or domain app feature work—use repo-quality-system-lifecycle or native product gates.\nlicense: MIT\ntype: governance\nmetadata:\n  author: skill-steward\n  version: \"1.2.0\"\n  category: harness\npaths:\n  - \"CHANGELOG.md\"\n  - \".changeset\u002F**\"\n  - \"package.json\"\n  - \"pnpm-workspace.yaml\"\n  - \"pubspec.yaml\"\n  - \"Cargo.toml\"\n  - \".github\u002Fworkflows\u002F*release*\"\n  - \".github\u002Fworkflows\u002F*publish*\"\n---\n\n# Release & changelog harness\n\nMake **releases understandable**: every version bump has structured intent that agents and humans can read in git—not only in a maintainer’s head or a GitHub Releases textarea.\n\nThis skill is **meta harness culture** (which tool, which gates, which docs). It is **not** a full tutorial for every package manager. Ordinary work: [work discipline](references\u002Fwork-discipline.md). The former `plugin-marketplace-setup` skill was removed in 0.6.0.\n\n## Mixture of experts — critique your idea\n\n| Expert lens | Verdict on “use JS Changesets everywhere” |\n|-------------|-------------------------------------------|\n| **JS monorepo maintainer** | Strong default: `.changeset\u002F*.md` + `changeset version` beats hand-editing five `package.json` files. |\n| **Dart \u002F Flutter publisher** | Weak fit as-is: pub uses tags + `CHANGELOG.md`; monorepos often use **Melos** `version` \u002F `changelog`, not npm Changesets. |\n| **Rust \u002F Go shipper** | Use **release-plz**, **cargo-release**, or **git-cliff**—forcing Changesets adds alien workflow. |\n| **Agent operator** | Wins when notes live as **small structured files in git** agents can read and PR—not prose-only in Slack. |\n| **Multi-repo steward (`~\u002Fmcp`)** | One **legibility contract** across siblings; **different generators** per ecosystem is fine. |\n| **Skill Steward charter** | Teach **when + gate + doc placement**; link to upstream docs; do not paste 200-line configs into `SKILL.md`. |\n\n**Improved framing (use this):**\n\n> Adopt the **release legibility contract** first; pick the **ecosystem-native generator** second (Changesets is one excellent generator for JS workspaces, not the universal hammer).\n\nSee [mixture-of-experts.md](references\u002Fmixture-of-experts.md) for extended debate and anti-patterns.\n\n## Release legibility contract (normative)\n\nBefore picking a tool, agree the repo obeys:\n\n1. **Notes in git** — Changelog or changeset files are versioned; not release-notes-only in a web UI.\n2. **Structured contributor input** — Contributors add intent in a **fixed shape** (e.g. `.changeset\u002Ffoo.md`, conventional commit scope, or ADR note)—not “bump version when you remember.”\n3. **Mechanical publish path** — One documented command sequence in **DX_FAQ**; CI is the source of truth for “can ship.”\n4. **Agent-readable output** — Post-release, `CHANGELOG.md` (or per-package changelogs) reflects what shipped; agents can answer “what changed in vX?”\n5. **Why is recorded** — Non-obvious toolchain choice → short **ADR** or DESIGN_FAQ Q&A.\n6. **Install trust matches release truth** — The latest GitHub Release, release assets, checksums, package versions, and install docs must agree; stale pinned install examples are release drift.\n\n## Ecosystem router (default patterns)\n\n| Signal in repo | Default tooling | Notes |\n|----------------|-----------------|-------|\n| `pnpm-workspace.yaml` \u002F npm workspaces | [@changesets\u002Fcli](https:\u002F\u002Fgithub.com\u002Fchangesets\u002Fchangesets) | Industry standard for JS monorepos; pair with GitHub Action. |\n| Single Node package, high release cadence | [release-please](https:\u002F\u002Fgithub.com\u002Fgoogleapis\u002Frelease-please) or Changesets | release-please = conventional commits → PR; Changesets = explicit human\u002Fagent intent files. |\n| Dart monorepo (`melos.yaml`) | [Melos](https:\u002F\u002Fmelos.invertase.dev\u002F) `version` + changelog | Align with pub publish order in DX_FAQ. |\n| Single Dart package | `CHANGELOG.md` + git tag + `dart pub publish` | Keep entries agent-editable markdown. |\n| Rust workspace | [release-plz](https:\u002F\u002Fgithub.com\u002FMarcoIeni\u002Frelease-plz) or cargo-release + git-cliff | Prefer automation that opens version PRs. |\n| Product harness w\u002F binaries | release-please + tag CI + `install.sh` | **Do not** add a second version source; follow [binary-release-contract.md](references\u002Fbinary-release-contract.md) |\n| Meta + CLI binary (Skill Steward) | Changesets + single Release workflow + `install.sh` | Version PR updates git truth first; the release workflow tags, builds assets, creates\u002Fupdates GitHub Release, and verifies latest\u002Finstall trust per [ADR 0014](..\u002F..\u002Fdocs\u002Fdecisions\u002F0014-distribute-steward-cli-as-binary.mdx) |\n\nFull matrix: [ecosystem-tooling.md](references\u002Fecosystem-tooling.md). Binary\u002Finstall: [binary-release-contract.md](references\u002Fbinary-release-contract.md).\n\n## When to use this skill\n\n- “We should use Changesets like the JS community”\n- Release process is unclear, versions drift, or agents can’t tell what shipped\n- Adding release CI, versioning policy, or monorepo publish workflow\n- Auditing whether changelog tooling matches repo archetype (`repo-quality-system-lifecycle`)\n\n## Workflow\n\n### 1. Classify the repo\n\nUse `repo-quality-system-lifecycle` archetypes (app, library, CLI\u002Ftool, plugin, harness, meta\u002Fgovernance). **Meta and harness repos** need legibility; **app repos** need legibility **and** runtime compatibility notes.\n\n### 2. Choose generator (ADR if non-obvious)\n\n| Question | If yes → |\n|----------|----------|\n| Multiple publishable JS packages? | Changesets (default) |\n| Single package, commit-msg driven releases? | release-please |\n| Maintainer writes explicit release notes per PR? | Changesets |\n| Pub or Cargo primary? | Ecosystem table above—not Changesets |\n\nRecord choice in `docs\u002Fdecisions\u002FNNNN-release-changelog-tooling.md` when more than one option is reasonable.\n\n### 3. Wire harness surfaces\n\n| Surface | Action |\n|---------|--------|\n| **DX_FAQ** | Memory-palace block: add changeset, version, publish, verify tag |\n| **CI** | Block publish\u002Ftag if changesets\u002Fchangelog policy violated; for binaries, use one release owner or an explicit workflow_run\u002FPAT handoff |\n| **AGENTS.md** | One row in doc router—no full Changesets essay |\n| **CONTRIBUTING** | “Every user-facing PR adds a changeset or CHANGELOG entry” |\n\n### 4. Minimal Changesets shape (JS monorepos and private packages)\n\nContributor adds:\n\n```markdown\n---\n\"package-name\": patch\n---\n\nShort imperative summary agents can quote in release notes.\n```\n\n#### Private Packages and Public Tags\nBy default, Changesets ignores packages marked with `\"private\": true` in `package.json`. To allow version bumps for a private root package or private workspace modules, update `.changeset\u002Fconfig.json` to include:\n\n```json\n  \"privatePackages\": {\n    \"version\": true,\n    \"tag\": false\n  }\n```\n\nUse `\"tag\": false` when a custom release script owns the public `vX.Y.Z` tag. Use `\"tag\": true` only when Changesets itself should create package-scoped tags.\n\nMaintainer flow:\n\n```bash\npnpm changeset          # or npx @changesets\u002Fcli\npnpm changeset version\npnpm install            # if lockfile must update\ngit commit -am \"chore: version packages\"\n```\n\nPublish: project-specific (`changeset publish`, GitHub Action, or npm provenance)—**document exact commands in DX_FAQ**, not here.\n\nFor automated Changesets releases, prefer:\n\n```text\nmerge feature PR with changeset\n→ CI opens\u002Fupdates Version PR\n→ merge Version PR\n→ same Release workflow creates vX.Y.Z, builds artifacts, creates\u002Fupdates GitHub Release, verifies latest release state\n```\n\nIf the tag is pushed with `GITHUB_TOKEN`, do not depend on a separate `on: push: tags` workflow to build assets; GitHub suppresses recursive workflow triggers for that token.\n\n### 5. Choose distribution surface\n\n| Ship unit | Pattern |\n|-----------|---------|\n| Executable MCP\u002FCLI | GitHub Release binaries + checksums + `install.sh` — [binary-release-contract.md](references\u002Fbinary-release-contract.md) |\n| Skills only | `npx skills add owner\u002Frepo` — no repo tarball for consumers |\n| Libraries | pub.dev \u002F npm \u002F crates.io per ecosystem table |\n\n**Skill Steward:** skills via `npx skills`; `steward_cli` precompiled AOT binaries via GitHub Releases & `install.sh` ([ADR 0014](..\u002F..\u002Fdocs\u002Fdecisions\u002F0014-distribute-steward-cli-as-binary.mdx)).\n\n### 6. Verify legibility\n\n- [ ] Agent can read “what’s unreleased” from git without GitHub API\n- [ ] CI fails when a version bump lacks notes\n- [ ] DX_FAQ lists commands copy-paste ready\n- [ ] No duplicate version sources (e.g. hand bump + bot bump)\n- [ ] If binaries: tag assets match version SSOT; latest GitHub Release points to the package version; `install.sh` defaults to latest and pinned examples use placeholders or generated checks\n\n## Anti-patterns\n\n| Anti-pattern | Why it hurts |\n|--------------|--------------|\n| Changesets in a Rust-only repo | Wrong culture; contributors ignore it |\n| Changelog only on GitHub Releases | Agents in repo context miss it |\n| 1,000-line release doc in AGENTS.md | Crowds task context; belongs in DX_FAQ \u002F ADR |\n| Skipping changesets “because AI will write CHANGELOG at release” | Non-deterministic; no PR-time review |\n| Version bumps without consumer-facing sentence | Users and agents can’t assess upgrade risk |\n| Binary Releases without changelog in git | Users see version; agents miss intent |\n| Separate tag-triggered binary workflow after a `GITHUB_TOKEN` tag push | GitHub suppresses recursive workflow triggers; latest release\u002Fassets can silently lag |\n| Static pinned install examples with real old versions | README\u002FDX says one thing while GitHub Releases\u002Finstall.sh say another |\n| `git clone` as end-user install for a server product | Use `install.sh` + Release assets (binary release pattern) |\n\n## Related skills\n\n| Skill | Use for |\n|-------|---------|\n| `repo-quality-system-lifecycle` | Repo archetype, mechanical gates, evidence path |\n| `repository-governance-lifecycle` | ADRs, DESIGN_FAQ\u002FDX_FAQ updates, and plan hygiene |\n\n## Install\n\n```bash\nnpx skills add arenukvern\u002Fskill_steward --skill release-changelog-harness\n```\n\n## Sources\n\n[references\u002Fsources.md](references\u002Fsources.md)\n","# Release & changelog harness\n\nMake **releases understandable**: every version bump has structured intent that agents and humans can read in git—not only in a maintainer’s head or a GitHub Releases textarea.\n\nThis skill is **meta harness culture** (which tool, which gates, which docs). It is **not** a full tutorial for every package manager. Ordinary work: [work discipline](references\u002Fwork-discipline.md). The former `plugin-marketplace-setup` skill was removed in 0.6.0.\n\n## Mixture of experts — critique your idea\n\n| Expert lens | Verdict on “use JS Changesets everywhere” |\n|-------------|-------------------------------------------|\n| **JS monorepo maintainer** | Strong default: `.changeset\u002F*.md` + `changeset version` beats hand-editing five `package.json` files. |\n| **Dart \u002F Flutter publisher** | Weak fit as-is: pub uses tags + `CHANGELOG.md`; monorepos often use **Melos** `version` \u002F `changelog`, not npm Changesets. |\n| **Rust \u002F Go shipper** | Use **release-plz**, **cargo-release**, or **git-cliff**—forcing Changesets adds alien workflow. |\n| **Agent operator** | Wins when notes live as **small structured files in git** agents can read and PR—not prose-only in Slack. |\n| **Multi-repo steward (`~\u002Fmcp`)** | One **legibility contract** across siblings; **different generators** per ecosystem is fine. |\n| **Skill Steward charter** | Teach **when + gate + doc placement**; link to upstream docs; do not paste 200-line configs into `SKILL.md`. |\n\n**Improved framing (use this):**\n\n> Adopt the **release legibility contract** first; pick the **ecosystem-native generator** second (Changesets is one excellent generator for JS workspaces, not the universal hammer).\n\nSee [mixture-of-experts.md](references\u002Fmixture-of-experts.md) for extended debate and anti-patterns.\n\n## Release legibility contract (normative)\n\nBefore picking a tool, agree the repo obeys:\n\n1. **Notes in git** — Changelog or changeset files are versioned; not release-notes-only in a web UI.\n2. **Structured contributor input** — Contributors add intent in a **fixed shape** (e.g. `.changeset\u002Ffoo.md`, conventional commit scope, or ADR note)—not “bump version when you remember.”\n3. **Mechanical publish path** — One documented command sequence in **DX_FAQ**; CI is the source of truth for “can ship.”\n4. **Agent-readable output** — Post-release, `CHANGELOG.md` (or per-package changelogs) reflects what shipped; agents can answer “what changed in vX?”\n5. **Why is recorded** — Non-obvious toolchain choice → short **ADR** or DESIGN_FAQ Q&A.\n6. **Install trust matches release truth** — The latest GitHub Release, release assets, checksums, package versions, and install docs must agree; stale pinned install examples are release drift.\n\n## Ecosystem router (default patterns)\n\n| Signal in repo | Default tooling | Notes |\n|----------------|-----------------|-------|\n| `pnpm-workspace.yaml` \u002F npm workspaces | [@changesets\u002Fcli](https:\u002F\u002Fgithub.com\u002Fchangesets\u002Fchangesets) | Industry standard for JS monorepos; pair with GitHub Action. |\n| Single Node package, high release cadence | [release-please](https:\u002F\u002Fgithub.com\u002Fgoogleapis\u002Frelease-please) or Changesets | release-please = conventional commits → PR; Changesets = explicit human\u002Fagent intent files. |\n| Dart monorepo (`melos.yaml`) | [Melos](https:\u002F\u002Fmelos.invertase.dev\u002F) `version` + changelog | Align with pub publish order in DX_FAQ. |\n| Single Dart package | `CHANGELOG.md` + git tag + `dart pub publish` | Keep entries agent-editable markdown. |\n| Rust workspace | [release-plz](https:\u002F\u002Fgithub.com\u002FMarcoIeni\u002Frelease-plz) or cargo-release + git-cliff | Prefer automation that opens version PRs. |\n| Product harness w\u002F binaries | release-please + tag CI + `install.sh` | **Do not** add a second version source; follow [binary-release-contract.md](references\u002Fbinary-release-contract.md) |\n| Meta + CLI binary (Skill Steward) | Changesets + single Release workflow + `install.sh` | Version PR updates git truth first; the release workflow tags, builds assets, creates\u002Fupdates GitHub Release, and verifies latest\u002Finstall trust per [ADR 0014](..\u002F..\u002Fdocs\u002Fdecisions\u002F0014-distribute-steward-cli-as-binary.mdx) |\n\nFull matrix: [ecosystem-tooling.md](references\u002Fecosystem-tooling.md). Binary\u002Finstall: [binary-release-contract.md](references\u002Fbinary-release-contract.md).\n\n## When to use this skill\n\n- “We should use Changesets like the JS community”\n- Release process is unclear, versions drift, or agents can’t tell what shipped\n- Adding release CI, versioning policy, or monorepo publish workflow\n- Auditing whether changelog tooling matches repo archetype (`repo-quality-system-lifecycle`)\n\n## Workflow\n\n### 1. Classify the repo\n\nUse `repo-quality-system-lifecycle` archetypes (app, library, CLI\u002Ftool, plugin, harness, meta\u002Fgovernance). **Meta and harness repos** need legibility; **app repos** need legibility **and** runtime compatibility notes.\n\n### 2. Choose generator (ADR if non-obvious)\n\n| Question | If yes → |\n|----------|----------|\n| Multiple publishable JS packages? | Changesets (default) |\n| Single package, commit-msg driven releases? | release-please |\n| Maintainer writes explicit release notes per PR? | Changesets |\n| Pub or Cargo primary? | Ecosystem table above—not Changesets |\n\nRecord choice in `docs\u002Fdecisions\u002FNNNN-release-changelog-tooling.md` when more than one option is reasonable.\n\n### 3. Wire harness surfaces\n\n| Surface | Action |\n|---------|--------|\n| **DX_FAQ** | Memory-palace block: add changeset, version, publish, verify tag |\n| **CI** | Block publish\u002Ftag if changesets\u002Fchangelog policy violated; for binaries, use one release owner or an explicit workflow_run\u002FPAT handoff |\n| **AGENTS.md** | One row in doc router—no full Changesets essay |\n| **CONTRIBUTING** | “Every user-facing PR adds a changeset or CHANGELOG entry” |\n\n### 4. Minimal Changesets shape (JS monorepos and private packages)\n\nContributor adds:\n\n```markdown\n---\n\"package-name\": patch\n---\n\nShort imperative summary agents can quote in release notes.\n```\n\n#### Private Packages and Public Tags\nBy default, Changesets ignores packages marked with `\"private\": true` in `package.json`. To allow version bumps for a private root package or private workspace modules, update `.changeset\u002Fconfig.json` to include:\n\n```json\n  \"privatePackages\": {\n    \"version\": true,\n    \"tag\": false\n  }\n```\n\nUse `\"tag\": false` when a custom release script owns the public `vX.Y.Z` tag. Use `\"tag\": true` only when Changesets itself should create package-scoped tags.\n\nMaintainer flow:\n\n```bash\npnpm changeset          # or npx @changesets\u002Fcli\npnpm changeset version\npnpm install            # if lockfile must update\ngit commit -am \"chore: version packages\"\n```\n\nPublish: project-specific (`changeset publish`, GitHub Action, or npm provenance)—**document exact commands in DX_FAQ**, not here.\n\nFor automated Changesets releases, prefer:\n\n```text\nmerge feature PR with changeset\n→ CI opens\u002Fupdates Version PR\n→ merge Version PR\n→ same Release workflow creates vX.Y.Z, builds artifacts, creates\u002Fupdates GitHub Release, verifies latest release state\n```\n\nIf the tag is pushed with `GITHUB_TOKEN`, do not depend on a separate `on: push: tags` workflow to build assets; GitHub suppresses recursive workflow triggers for that token.\n\n### 5. Choose distribution surface\n\n| Ship unit | Pattern |\n|-----------|---------|\n| Executable MCP\u002FCLI | GitHub Release binaries + checksums + `install.sh` — [binary-release-contract.md](references\u002Fbinary-release-contract.md) |\n| Skills only | `npx skills add owner\u002Frepo` — no repo tarball for consumers |\n| Libraries | pub.dev \u002F npm \u002F crates.io per ecosystem table |\n\n**Skill Steward:** skills via `npx skills`; `steward_cli` precompiled AOT binaries via GitHub Releases & `install.sh` ([ADR 0014](..\u002F..\u002Fdocs\u002Fdecisions\u002F0014-distribute-steward-cli-as-binary.mdx)).\n\n### 6. Verify legibility\n\n- [ ] Agent can read “what’s unreleased” from git without GitHub API\n- [ ] CI fails when a version bump lacks notes\n- [ ] DX_FAQ lists commands copy-paste ready\n- [ ] No duplicate version sources (e.g. hand bump + bot bump)\n- [ ] If binaries: tag assets match version SSOT; latest GitHub Release points to the package version; `install.sh` defaults to latest and pinned examples use placeholders or generated checks\n\n## Anti-patterns\n\n| Anti-pattern | Why it hurts |\n|--------------|--------------|\n| Changesets in a Rust-only repo | Wrong culture; contributors ignore it |\n| Changelog only on GitHub Releases | Agents in repo context miss it |\n| 1,000-line release doc in AGENTS.md | Crowds task context; belongs in DX_FAQ \u002F ADR |\n| Skipping changesets “because AI will write CHANGELOG at release” | Non-deterministic; no PR-time review |\n| Version bumps without consumer-facing sentence | Users and agents can’t assess upgrade risk |\n| Binary Releases without changelog in git | Users see version; agents miss intent |\n| Separate tag-triggered binary workflow after a `GITHUB_TOKEN` tag push | GitHub suppresses recursive workflow triggers; latest release\u002Fassets can silently lag |\n| Static pinned install examples with real old versions | README\u002FDX says one thing while GitHub Releases\u002Finstall.sh say another |\n| `git clone` as end-user install for a server product | Use `install.sh` + Release assets (binary release pattern) |\n\n## Related skills\n\n| Skill | Use for |\n|-------|---------|\n| `repo-quality-system-lifecycle` | Repo archetype, mechanical gates, evidence path |\n| `repository-governance-lifecycle` | ADRs, DESIGN_FAQ\u002FDX_FAQ updates, and plan hygiene |\n\n## Install\n\n```bash\nnpx skills add arenukvern\u002Fskill_steward --skill release-changelog-harness\n```\n\n## Sources\n\n[references\u002Fsources.md](references\u002Fsources.md)\n",{"name":5,"type":24,"paths":25,"license":15,"metadata":34,"description":7},"governance",[26,27,28,29,30,31,32,33],"CHANGELOG.md",".changeset\u002F**","package.json","pnpm-workspace.yaml","pubspec.yaml","Cargo.toml",".github\u002Fworkflows\u002F*release*",".github\u002Fworkflows\u002F*publish*",{"author":35,"version":36,"category":37},"skill-steward","1.2.0","harness","main","ab91839b44569fc3d51d3390d8c81c2f825be6fd","skills\u002Frelease-changelog-harness",2,"https:\u002F\u002Fgithub.com\u002FArenukvern\u002Fskill_steward","https:\u002F\u002Fdocs.page\u002Farenukvern\u002Fskill_steward","https:\u002F\u002Fgithub.com\u002FArenukvern","https:\u002F\u002Fxsoulspace.dev","Software Engineer & Enthusiast. Making useful (hope so:)) apps with Flutter & Dart","2026-11-15 03:14:36",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add Arenukvern\u002Fskill_steward --skill release-changelog-harness",{"tool":54,"command":55},"bunx","bunx skills add Arenukvern\u002Fskill_steward --skill release-changelog-harness",{"tool":57,"command":58},"pnpm","pnpm dlx skills add Arenukvern\u002Fskill_steward --skill release-changelog-harness","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FArenukvern\u002Fskill_steward\u002Fblob\u002Fmain\u002Fskills\u002Frelease-changelog-harness\u002FSKILL.md",true,[62,68,72,76,80],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fbinary-release-contract.md","REFERENCE","参考文档",10410,"https:\u002F\u002Fgithub.com\u002FArenukvern\u002Fskill_steward\u002Fblob\u002Fmain\u002Fskills\u002Frelease-changelog-harness\u002Freferences\u002Fbinary-release-contract.md",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fecosystem-tooling.md",3159,"https:\u002F\u002Fgithub.com\u002FArenukvern\u002Fskill_steward\u002Fblob\u002Fmain\u002Fskills\u002Frelease-changelog-harness\u002Freferences\u002Fecosystem-tooling.md",{"path":73,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fmixture-of-experts.md",2928,"https:\u002F\u002Fgithub.com\u002FArenukvern\u002Fskill_steward\u002Fblob\u002Fmain\u002Fskills\u002Frelease-changelog-harness\u002Freferences\u002Fmixture-of-experts.md",{"path":77,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fsources.md",1743,"https:\u002F\u002Fgithub.com\u002FArenukvern\u002Fskill_steward\u002Fblob\u002Fmain\u002Fskills\u002Frelease-changelog-harness\u002Freferences\u002Fsources.md",{"path":81,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fwork-discipline.md",932,"https:\u002F\u002Fgithub.com\u002FArenukvern\u002Fskill_steward\u002Fblob\u002Fmain\u002Fskills\u002Frelease-changelog-harness\u002Freferences\u002Fwork-discipline.md",[85,92,99,106,113,120],{"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},"01M75476ZMYBC2JX2RE1W2651K","your-skill-name","Replace with what this skill does and when to use it. Include trigger phrases users say, e.g. \"audit my API\", \"scaffold a skill\"; activation-critical routing belongs here.","https:\u002F\u002Fgithub.com\u002FArenukvern\u002Fskill_steward\u002Fblob\u002Fmain\u002Ftemplates\u002Fskill\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},"01M75471BJP801A924Q9CW6Q33","skill-authoring-lifecycle","For creating or editing installable Agent Skills, eval cases, citations, and marketplace\u002Fregistry readiness in this repo. Not for adopting consumer repos, governance ADRs, or release automation—use repo-quality-system-lifecycle, repository-governance-lifecycle, or release-changelog-harness.","https:\u002F\u002Fgithub.com\u002FArenukvern\u002Fskill_steward\u002Fblob\u002Fmain\u002Fskills\u002Fskill-authoring-lifecycle\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7546VV8KXF21X8WGM38DR95","repository-governance-lifecycle","For ADRs, DESIGN\u002FDX FAQ edits, north_star_impact, stale-plan hygiene, ethics, brand tone, MoE on governance conflicts, and doc-lattice changes that outlive one repair. Not for repo adopt\u002Fbaseline, ecology compress\u002Fmerge\u002Fretire, or product feature work—use repo-quality-system-lifecycle or native gates.","https:\u002F\u002Fgithub.com\u002FArenukvern\u002Fskill_steward\u002Fblob\u002Fmain\u002Fskills\u002Frepository-governance-lifecycle\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7546P7MQ4S22E33GEBEC5J1","repo-quality-system-lifecycle","For adopt\u002Fbaseline, stewardship quality-contract audits, evidence and maturity proof, producer\u002Fconsumer boundaries, repo ecology compress\u002Fmerge\u002Fretire, and claim-honesty reviews. Not for ADR\u002FFAQ-only governance, harness generalization after baseline, release CI, skill packaging, or routine product repairs with a known native gate.","https:\u002F\u002Fgithub.com\u002FArenukvern\u002Fskill_steward\u002Fblob\u002Fmain\u002Fskills\u002Frepo-quality-system-lifecycle\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M7546CNMEZEP2JBXTKRRZQH6","multi-agent-handoff","For baton handoffs, one-obligation moves between agents, and parent-lane or parallel-batch contracts when multiple subagents share work. Not for repo adopt, ADRs, ecology cleanup, or product implementation—use repo-quality-system-lifecycle, repository-governance-lifecycle, or native work.","https:\u002F\u002Fgithub.com\u002FArenukvern\u002Fskill_steward\u002Fblob\u002Fmain\u002Fskills\u002Fmulti-agent-handoff\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":19},"01M75467J8RX8A7CF2254XSE3T","harness-engineering-lifecycle","For generalizing a proven local steward.yaml harness across producer-consumer repos, polyrepo CLI\u002FMCP integration, and sibling-repo dogfood after a contract exists. Not for cold-start adoption, first steward.yaml, first quick probe, or skill packaging—use repo-quality-system-lifecycle or skill-authoring-lifecycle.","https:\u002F\u002Fgithub.com\u002FArenukvern\u002Fskill_steward\u002Fblob\u002Fmain\u002Fskills\u002Fharness-engineering-lifecycle\u002FSKILL.md",[],[]]