[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NPQ3R3RQW0F1HSBV76WHNA":3,"skill-same:01M6NPQ3R3RQW0F1HSBV76WHNA":98},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":14,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":68,"install":69,"resources":82},"01M6NPQ3R3RQW0F1HSBV76WHNA","release-semver",null,"Semantic versioning releases — version bumps, changelogs, tags, publishing. Use when preparing a new release: deciding the version bump, drafting the changelog, tagging the commit, and publishing to the project's distribution channel.","projectious-work\u002Fprocesskit","projectious-work","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263889726?v=4","01M6N97TJJ118WQ35CHRV8RD0E","projectious.work","01M6N97TPWJPF0BMKYQ4PBY5W8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdevops\u002Frelease-semver\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"release semver","semver","release","phase","when","work","create","publish","draft","type","tags","commit","patch","version","number","use","publishing","bump","project","distribution","2026-11-10 10:12:30",false,"---\nname: release-semver\ndescription: |\n  Semantic versioning releases — version bumps, changelogs, tags, publishing. Use when preparing a new release: deciding the version bump, drafting the changelog, tagging the commit, and publishing to the project's distribution channel.\nmetadata:\n  processkit:\n    apiVersion: processkit.projectious.work\u002Fv2\n    id: SKILL-release-semver\n    version: \"1.2.0\"\n    created: 2026-04-06T00:00:00Z\n    category: devops\n    layer: 3\n    commands:\n      - name: pk-release\n        args: \"bump-type (major, minor, patch, or version number)\"\n        description: \"Prepare a release: bump version, draft changelog, create tag.\"\n      - name: pk-publish\n        args: \"\"\n        description: \"Execute the publish phase of the prepared release.\"\n---\n\n# Semantic Versioning Release Process\n\n## Intro\n\nReleases are routine, not heroic. Decide the version bump from the\nnature of the changes, draft a changelog, update version files in\none commit, tag with `vX.Y.Z`, and publish. The goal is a release\nanyone on the team can perform from the same checklist.\n\n## Overview\n\n### Determine the version bump\n\nSemantic versioning has three numbers: MAJOR.MINOR.PATCH.\n\n- **Patch** (0.1.0 → 0.1.1): bug fixes only, no API changes.\n- **Minor** (0.1.0 → 0.2.0): new features, backward-compatible.\n- **Major** (0.1.0 → 1.0.0): breaking changes.\n\nPre-1.0 projects bend the rules: minor bumps are allowed to break\ncompatibility, and patch bumps cover both features and fixes. Once\nyou ship 1.0, the rules become strict.\n\n### Pre-release checklist\n\n- All tests pass on the designated release-integration branch.\n- No uncommitted changes in the working tree.\n- Dependencies reviewed and up to date where appropriate.\n- `CHANGELOG.md` has a curated, dated section for the exact release tag;\n  it includes only user-visible changes, uses standard categories, and has\n  correct comparison links.\n- A root `LICENSE` file exists and matches the intended project\n  license. If the project ships release archives, the archive build must\n  include that `LICENSE` at the top level. For processkit,\n  `scripts\u002Fbuild-release-tarball.sh` copies root `LICENSE` into\n  `processkit-vX.Y.Z\u002F`.\n\n### Draft the changelog\n\nGroup entries under **Added**, **Changed**, **Fixed**, and\n**Removed**. Reference issue and PR numbers. Note breaking changes\nprominently — call them out in their own section if a major bump\nis involved.\n\n### The release flow (single turn, bulletproof)\n\nA release is **one continuous sequence** — you do not stop halfway.\n`\u002Fpk-release vX.Y.Z` runs every step below in order, in the same\nturn, and is not considered done until the final verification\npasses. See DEC-20260422_1348-SnowyWolf.\n\n1. **Bump version** in every relevant file (`aibox.lock`,\n   `Cargo.toml`, `pyproject.toml`, `package.json`, lockfiles).\n2. **Finalize CHANGELOG** — rename the `[vX.Y.Z-candidate]` section\n   to `[vX.Y.Z] — YYYY-MM-DD`; ensure Added\u002FChanged\u002FFixed\u002FRemoved\n   grouping; call out breaking changes if a major bump. Confirm the\n   root `CHANGELOG.md` contains a `## [vX.Y.Z]` heading; the archive\n   build rejects a release without it.\n3. **Regenerate provenance \u002F transitive artifacts** — for processkit,\n   `scripts\u002Fstamp-provenance.sh vX.Y.Z`.\n4. **Commit** the bump with message `chore(release): bump to vX.Y.Z`.\n5. **Tag** the commit: `git tag -a vX.Y.Z -m \"\u003Ctag summary>\"`.\n6. **Merge, then tag.** Prepare steps 1–4 on `release\u002FvX.Y.Z`, squash-merge\n   it into `main` (or its `lts\u002F*` line) after approval, then tag the squash\n   commit and push the tag.\n   A tag push alone does **not** create a GitHub Release — it is a\n   git ref, not a distribution-channel artifact.\n7. **Create the GitHub Release** with notes extracted from the\n   CHANGELOG and attach the release archive plus checksum when the\n   project produces binary\u002Farchive assets. For processkit, build first\n   with `scripts\u002Fbuild-release-tarball.sh vX.Y.Z`; the tarball must\n   contain top-level `LICENSE` and `CHANGELOG.md`. The tag commit must\n   also contain root `LICENSE`, so GitHub's generated source archives\n   carry the license. The single canonical command:\n   ```bash\n   gh release create vX.Y.Z \\\n     dist\u002Fprocesskit-vX.Y.Z.tar.gz \\\n     dist\u002Fprocesskit-vX.Y.Z.tar.gz.sha256 \\\n     --repo \u003Corg>\u002F\u003Crepo> \\\n     --title \"vX.Y.Z — \u003Cone-line summary>\" \\\n     --notes-file \u003C(awk -v v=X.Y.Z '\n       $0 ~ \"^## \\\\[v\" v \"\\\\]\"   { f=1; next }\n       f && \u002F^## \\[\u002F              { f=0 }\n       f\n     ' CHANGELOG.md) \\\n     --latest\n   ```\n8. **Verify** the Release is live. This is the release's\n   completion gate. For archive-based releases, verify the Release has\n   the expected tarball\u002Fchecksum assets and that extracting the tarball\n   shows a top-level `LICENSE`; also verify the tag itself contains\n   root `LICENSE`:\n   ```bash\n   gh release view vX.Y.Z --repo \u003Corg>\u002F\u003Crepo>\n   tar -tzf dist\u002Fprocesskit-vX.Y.Z.tar.gz | grep '\u002FLICENSE$'\n   git show vX.Y.Z:LICENSE >\u002Fdev\u002Fnull\n   ```\n   If this exits non-zero, the release is **incomplete** — return\n   to step 7. Do not report the release as done until step 8\n   succeeds.\n9. **Other channels** (crates.io, PyPI, npm, container registry,\n   homebrew tap, etc.) — run after step 8 so the GitHub Release\n   remains the canonical artifact pointer.\n\n**Recovery pattern** — if a tag was pushed in a prior session\nwithout the Release, run `gh release create` and `gh release view`\nfor that tag directly; `\u002Fpk-publish` exists as an alias for this\nrecovery scenario.\n\n**pk-doctor `release_integrity` check (detection layer)** — walks\nevery local `v*` git tag, probes GitHub for a matching Release, and\nWARNs on any tag without one. Run `\u002Fpk-doctor --category=release_integrity`\nafter a release to confirm; run `\u002Fpk-doctor` routinely to catch any\nhistorical gap. Requires `gh` CLI + auth; emits INFO when `gh` is\nunavailable.\n\n### Example\n\nUser says: \"Let's release — we fixed two bugs and added a feature.\"\nThe agent recommends a minor bump (because of the new feature),\ndrafts changelog entries grouped Added\u002FFixed, updates version\nfiles, creates the bump commit, and tags it.\n\nThis skill also provides the `\u002Fpk-release` and `\u002Fpk-publish` commands\nfor direct invocation — see `commands\u002Fpk-release.md` and\n`commands\u002Fpk-publish.md`.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Bundling a breaking change into a patch or minor release.** Consumers rely on semver guarantees to control when they take breaking changes. A breaking change in a patch release violates the contract and causes silent runtime failures in consumer code.\n- **Skipping the changelog because \"git log has it\".** Git log is not a changelog. It lacks context, grouping, and the human judgment that makes a changelog useful. Every release needs a curated changelog with Added\u002FChanged\u002FFixed\u002FRemoved sections.\n- **Bumping all version files in separate commits.** A brief window where `Cargo.toml` says `1.2.0` but `pyproject.toml` still says `1.1.0` is a broken state. Update all version files in a single atomic commit.\n- **Tagging before CI passes.** A tag should point to a commit that has been fully built and tested. Tagging a commit that later fails CI means the published artifact may not match what was verified.\n- **Publishing from a developer machine without a clean checkout.** Uncommitted local changes — WIP files, debug flags, `console.log` statements — may sneak into the artifact. Publish from CI with a clean checkout or from a fresh clone.\n- **Re-tagging a published version to fix a mistake.** Package registries (crates.io, PyPI, npm) prohibit or block re-publishing to an existing version. Cut a new patch version (e.g. `1.2.1`) to fix a mistake in `1.2.0`; never overwrite a tag.\n- **Pre-1.0 projects that promise stability they cannot keep.** If the API is still moving, stay below 1.0 and say so. Cutting `1.0.0` too early creates a compatibility obligation that slows future improvements.\n- **Treating `git push --tags` as \"the release is out.\"** Pushing a tag creates a git ref; it does **not** create a GitHub Release, a crates.io release, a PyPI release, or any other distribution-channel artifact. Downstream consumers (package managers, `gh api`, the Releases page, auto-sync tools like aibox) read from the channel, not the tag. Until `gh release create` (or the equivalent channel publish command) has run, the release is not visible. The flow above bakes this in: the release is not complete until step 8 (`gh release view`) succeeds. See DEC-20260422_1348-SnowyWolf.\n- **Stopping after `\u002Fpk-release` prepare-like work.** In an older split where `\u002Fpk-release` prepared and `\u002Fpk-publish` published, it was easy to do only half. The current flow is single-turn: \u002Fpk-release runs every step through GitHub-Release verification. \u002Fpk-publish remains only as a recovery alias for historical tags without Releases.\n\n## Full reference\n\n### When pre-1.0 ends\n\nCut 1.0 when the public API is something you are willing to\nsupport without breaking. Until then, keep the version below 1.0\nhonestly — there is no shame in 0.17.0, and it signals to users\nthat the surface may still move.\n\n### Version bumps for special changes\n\n| Change | Bump |\n|---|---|\n| Bug fix that does not change behavior contract | patch |\n| Performance improvement, no API change | patch |\n| New feature behind a feature flag | minor |\n| New optional parameter with a default | minor |\n| Removing or renaming a public symbol | major |\n| Changing default behavior of an existing API | major |\n| Tightening input validation that rejects previously valid input | major |\n| Dependency bump that surfaces in your public API | major |\n\n### Anti-patterns\n\n- Bundling breaking changes into a patch release\n- Skipping the changelog \"because git log has it\"\n- Tagging a commit that was not built and tested\n- Publishing from a developer machine without a clean checkout\n- Re-tagging a published version to fix a mistake (cut a new\n  patch instead)\n- Pre-1.0 projects that promise stability they cannot keep\n","# Semantic Versioning Release Process\n\n## Intro\n\nReleases are routine, not heroic. Decide the version bump from the\nnature of the changes, draft a changelog, update version files in\none commit, tag with `vX.Y.Z`, and publish. The goal is a release\nanyone on the team can perform from the same checklist.\n\n## Overview\n\n### Determine the version bump\n\nSemantic versioning has three numbers: MAJOR.MINOR.PATCH.\n\n- **Patch** (0.1.0 → 0.1.1): bug fixes only, no API changes.\n- **Minor** (0.1.0 → 0.2.0): new features, backward-compatible.\n- **Major** (0.1.0 → 1.0.0): breaking changes.\n\nPre-1.0 projects bend the rules: minor bumps are allowed to break\ncompatibility, and patch bumps cover both features and fixes. Once\nyou ship 1.0, the rules become strict.\n\n### Pre-release checklist\n\n- All tests pass on the designated release-integration branch.\n- No uncommitted changes in the working tree.\n- Dependencies reviewed and up to date where appropriate.\n- `CHANGELOG.md` has a curated, dated section for the exact release tag;\n  it includes only user-visible changes, uses standard categories, and has\n  correct comparison links.\n- A root `LICENSE` file exists and matches the intended project\n  license. If the project ships release archives, the archive build must\n  include that `LICENSE` at the top level. For processkit,\n  `scripts\u002Fbuild-release-tarball.sh` copies root `LICENSE` into\n  `processkit-vX.Y.Z\u002F`.\n\n### Draft the changelog\n\nGroup entries under **Added**, **Changed**, **Fixed**, and\n**Removed**. Reference issue and PR numbers. Note breaking changes\nprominently — call them out in their own section if a major bump\nis involved.\n\n### The release flow (single turn, bulletproof)\n\nA release is **one continuous sequence** — you do not stop halfway.\n`\u002Fpk-release vX.Y.Z` runs every step below in order, in the same\nturn, and is not considered done until the final verification\npasses. See DEC-20260422_1348-SnowyWolf.\n\n1. **Bump version** in every relevant file (`aibox.lock`,\n   `Cargo.toml`, `pyproject.toml`, `package.json`, lockfiles).\n2. **Finalize CHANGELOG** — rename the `[vX.Y.Z-candidate]` section\n   to `[vX.Y.Z] — YYYY-MM-DD`; ensure Added\u002FChanged\u002FFixed\u002FRemoved\n   grouping; call out breaking changes if a major bump. Confirm the\n   root `CHANGELOG.md` contains a `## [vX.Y.Z]` heading; the archive\n   build rejects a release without it.\n3. **Regenerate provenance \u002F transitive artifacts** — for processkit,\n   `scripts\u002Fstamp-provenance.sh vX.Y.Z`.\n4. **Commit** the bump with message `chore(release): bump to vX.Y.Z`.\n5. **Tag** the commit: `git tag -a vX.Y.Z -m \"\u003Ctag summary>\"`.\n6. **Merge, then tag.** Prepare steps 1–4 on `release\u002FvX.Y.Z`, squash-merge\n   it into `main` (or its `lts\u002F*` line) after approval, then tag the squash\n   commit and push the tag.\n   A tag push alone does **not** create a GitHub Release — it is a\n   git ref, not a distribution-channel artifact.\n7. **Create the GitHub Release** with notes extracted from the\n   CHANGELOG and attach the release archive plus checksum when the\n   project produces binary\u002Farchive assets. For processkit, build first\n   with `scripts\u002Fbuild-release-tarball.sh vX.Y.Z`; the tarball must\n   contain top-level `LICENSE` and `CHANGELOG.md`. The tag commit must\n   also contain root `LICENSE`, so GitHub's generated source archives\n   carry the license. The single canonical command:\n   ```bash\n   gh release create vX.Y.Z \\\n     dist\u002Fprocesskit-vX.Y.Z.tar.gz \\\n     dist\u002Fprocesskit-vX.Y.Z.tar.gz.sha256 \\\n     --repo \u003Corg>\u002F\u003Crepo> \\\n     --title \"vX.Y.Z — \u003Cone-line summary>\" \\\n     --notes-file \u003C(awk -v v=X.Y.Z '\n       $0 ~ \"^## \\\\[v\" v \"\\\\]\"   { f=1; next }\n       f && \u002F^## \\[\u002F              { f=0 }\n       f\n     ' CHANGELOG.md) \\\n     --latest\n   ```\n8. **Verify** the Release is live. This is the release's\n   completion gate. For archive-based releases, verify the Release has\n   the expected tarball\u002Fchecksum assets and that extracting the tarball\n   shows a top-level `LICENSE`; also verify the tag itself contains\n   root `LICENSE`:\n   ```bash\n   gh release view vX.Y.Z --repo \u003Corg>\u002F\u003Crepo>\n   tar -tzf dist\u002Fprocesskit-vX.Y.Z.tar.gz | grep '\u002FLICENSE$'\n   git show vX.Y.Z:LICENSE >\u002Fdev\u002Fnull\n   ```\n   If this exits non-zero, the release is **incomplete** — return\n   to step 7. Do not report the release as done until step 8\n   succeeds.\n9. **Other channels** (crates.io, PyPI, npm, container registry,\n   homebrew tap, etc.) — run after step 8 so the GitHub Release\n   remains the canonical artifact pointer.\n\n**Recovery pattern** — if a tag was pushed in a prior session\nwithout the Release, run `gh release create` and `gh release view`\nfor that tag directly; `\u002Fpk-publish` exists as an alias for this\nrecovery scenario.\n\n**pk-doctor `release_integrity` check (detection layer)** — walks\nevery local `v*` git tag, probes GitHub for a matching Release, and\nWARNs on any tag without one. Run `\u002Fpk-doctor --category=release_integrity`\nafter a release to confirm; run `\u002Fpk-doctor` routinely to catch any\nhistorical gap. Requires `gh` CLI + auth; emits INFO when `gh` is\nunavailable.\n\n### Example\n\nUser says: \"Let's release — we fixed two bugs and added a feature.\"\nThe agent recommends a minor bump (because of the new feature),\ndrafts changelog entries grouped Added\u002FFixed, updates version\nfiles, creates the bump commit, and tags it.\n\nThis skill also provides the `\u002Fpk-release` and `\u002Fpk-publish` commands\nfor direct invocation — see `commands\u002Fpk-release.md` and\n`commands\u002Fpk-publish.md`.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Bundling a breaking change into a patch or minor release.** Consumers rely on semver guarantees to control when they take breaking changes. A breaking change in a patch release violates the contract and causes silent runtime failures in consumer code.\n- **Skipping the changelog because \"git log has it\".** Git log is not a changelog. It lacks context, grouping, and the human judgment that makes a changelog useful. Every release needs a curated changelog with Added\u002FChanged\u002FFixed\u002FRemoved sections.\n- **Bumping all version files in separate commits.** A brief window where `Cargo.toml` says `1.2.0` but `pyproject.toml` still says `1.1.0` is a broken state. Update all version files in a single atomic commit.\n- **Tagging before CI passes.** A tag should point to a commit that has been fully built and tested. Tagging a commit that later fails CI means the published artifact may not match what was verified.\n- **Publishing from a developer machine without a clean checkout.** Uncommitted local changes — WIP files, debug flags, `console.log` statements — may sneak into the artifact. Publish from CI with a clean checkout or from a fresh clone.\n- **Re-tagging a published version to fix a mistake.** Package registries (crates.io, PyPI, npm) prohibit or block re-publishing to an existing version. Cut a new patch version (e.g. `1.2.1`) to fix a mistake in `1.2.0`; never overwrite a tag.\n- **Pre-1.0 projects that promise stability they cannot keep.** If the API is still moving, stay below 1.0 and say so. Cutting `1.0.0` too early creates a compatibility obligation that slows future improvements.\n- **Treating `git push --tags` as \"the release is out.\"** Pushing a tag creates a git ref; it does **not** create a GitHub Release, a crates.io release, a PyPI release, or any other distribution-channel artifact. Downstream consumers (package managers, `gh api`, the Releases page, auto-sync tools like aibox) read from the channel, not the tag. Until `gh release create` (or the equivalent channel publish command) has run, the release is not visible. The flow above bakes this in: the release is not complete until step 8 (`gh release view`) succeeds. See DEC-20260422_1348-SnowyWolf.\n- **Stopping after `\u002Fpk-release` prepare-like work.** In an older split where `\u002Fpk-release` prepared and `\u002Fpk-publish` published, it was easy to do only half. The current flow is single-turn: \u002Fpk-release runs every step through GitHub-Release verification. \u002Fpk-publish remains only as a recovery alias for historical tags without Releases.\n\n## Full reference\n\n### When pre-1.0 ends\n\nCut 1.0 when the public API is something you are willing to\nsupport without breaking. Until then, keep the version below 1.0\nhonestly — there is no shame in 0.17.0, and it signals to users\nthat the surface may still move.\n\n### Version bumps for special changes\n\n| Change | Bump |\n|---|---|\n| Bug fix that does not change behavior contract | patch |\n| Performance improvement, no API change | patch |\n| New feature behind a feature flag | minor |\n| New optional parameter with a default | minor |\n| Removing or renaming a public symbol | major |\n| Changing default behavior of an existing API | major |\n| Tightening input validation that rejects previously valid input | major |\n| Dependency bump that surfaces in your public API | major |\n\n### Anti-patterns\n\n- Bundling breaking changes into a patch release\n- Skipping the changelog \"because git log has it\"\n- Tagging a commit that was not built and tested\n- Publishing from a developer machine without a clean checkout\n- Re-tagging a published version to fix a mistake (cut a new\n  patch instead)\n- Pre-1.0 projects that promise stability they cannot keep\n",{"name":5,"metadata":44,"description":61},{"processkit":45},{"id":46,"layer":47,"created":48,"version":49,"category":50,"commands":51,"apiVersion":60},"SKILL-release-semver",3,1775433600000,"1.2.0","devops",[52,56],{"args":53,"name":54,"description":55},"bump-type (major, minor, patch, or version number)","pk-release","Prepare a release: bump version, draft changelog, create tag.",{"args":57,"name":58,"description":59},"","pk-publish","Execute the publish phase of the prepared release.","processkit.projectious.work\u002Fv2","Semantic versioning releases — version bumps, changelogs, tags, publishing. Use when preparing a new release: deciding the version bump, drafting the changelog, tagging the commit, and publishing to the project's distribution channel.\n","main","4876a92620ee792aac2ac9a1a806322d8a572367","src\u002Fcontext\u002Fskills\u002Fdevops\u002Frelease-semver","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit","https:\u002F\u002Fprojectious-work.github.io\u002Fprocesskit\u002F","https:\u002F\u002Fgithub.com\u002Fprojectious-work","2026-11-11 23:24:18",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add projectious-work\u002Fprocesskit --skill release-semver",{"tool":75,"command":76},"bunx","bunx skills add projectious-work\u002Fprocesskit --skill release-semver",{"tool":78,"command":79},"pnpm","pnpm dlx skills add projectious-work\u002Fprocesskit --skill release-semver","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdevops\u002Frelease-semver\u002FSKILL.md",true,[83,89,93],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"commands\u002Fpk-publish.md","REFERENCE","参考文档",128,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdevops\u002Frelease-semver\u002Fcommands\u002Fpk-publish.md",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"commands\u002Fpk-release.md",308,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdevops\u002Frelease-semver\u002Fcommands\u002Fpk-release.md",{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":14,"sourceHtmlUrl":97},"scripts\u002F.gitkeep","SCRIPT","脚本","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdevops\u002Frelease-semver\u002Fscripts\u002F.gitkeep",[99,106,113,119,145,165],{"skillNo":100,"name":101,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":105},"01M7665G2ED3624R3X93304265","standard-ui-design","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-ui-design\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"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":105},"01M76651QTC6W0HJ4AFW2MMR3V","standard-agent-use","Company standard for working with AI agents. Use when deciding what to delegate to agents, capturing open work, keeping agent memory or knowledge notes, improving an agent workflow, or introducing agent work in a team or for a client.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-use\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":105},"01M76650NN4T8P241021NBR64S","standard-agent-building","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-building\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":130,"publishedAt":39},"01M6X5MTC89B4ZGXW3JVSQCPF8","skill-management","Manage Skill package manifests as v1 ontology entities.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-management\u002FSKILL.md",[125],{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[131,132,133,134,25,135,24,136,137,138,139,140,121,141,142,143,144],"management","skill management","ontology","v1","as","transition","get","manage","update","alpha","list","package","skill package","manifests",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":152,"publishedAt":39},"01M6X5MCV74NHW5MEDNHZRF2C8","schema-management","Manage generated processkit schema contracts through deterministic MCP rebuild and inspection workflows.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fschema-management\u002FSKILL.md",[151],{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},[153,154,131,155,156,157,158,159,160,161,162,163,24,137,138,140,164],"schema","schema management","contract","rebuild","contracts","workflows","wed","generated","MCP","validation","deterministic","mode",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":39},"01M6X5M5G6YJ96AMZGSCZJ1D13","proposition-management","Record claims, risks, beliefs, world facts, WSJF estimates, and assumptions through the Proposition interface.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fproposition-management\u002FSKILL.md",[],[172,131,173,174,25,175,176,177,24,137,178,179,139,180,140,181,182,183,184,185],"proposition management","proposition","interface","claims","record","world","creation","event","WSJF","index","updates","query","facts","log"]