[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77MDVH8D6Y5SPF72DXMYBS3":3,"skill-same:01M77MDVH8D6Y5SPF72DXMYBS3":50},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M77MDVH8D6Y5SPF72DXMYBS3","commits-and-releases",null,"Use when writing commit messages or splitting work into commits; when cutting, versioning, or tagging a release; when editing a CHANGELOG or bumping a version number; when setting up or fixing release-please, semantic-release, or changesets; or when a release has the wrong version or is missing changelog entries.","rahulmutt\u002Fdevkit","rahulmutt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F8035100?v=4","01M77MDP08WTFYCS2MD2Q580EJ","Rahul Muttineni","01M77MDP11EQ3MN8WV69GM6JKP",0,"MIT","https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit\u002Fblob\u002Fmain\u002Fskills\u002Fcommits-and-releases\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: commits-and-releases\ndescription: Use when writing commit messages or splitting work into commits; when cutting, versioning, or tagging a release; when editing a CHANGELOG or bumping a version number; when setting up or fixing release-please, semantic-release, or changesets; or when a release has the wrong version or is missing changelog entries.\n---\n\n# Commits and Releases\n\nCommit history is the input to the release: release tooling reads each commit\nsubject to pick the version bump and write the changelog. So a wrong release is\nfixed by changing that input, never the output.\n\nCommit format, breaking-change syntax, type-to-bump mapping, when to ship, and\nfixing merged history: see\n[`references\u002Frelease-please.md`](references\u002Frelease-please.md).\n\n## Releases come from history, not hand edits\n\nNever hand-edit the changelog, bump version strings or the manifest, or create\ntags that the release automation owns. That includes the files on the open\nrelease PR's branch: the next run regenerates them and your edit is lost or\ncontradicts history.\n\nFix a wrong release by changing what the tool reads:\n\n- **Wrong version:** add a commit on the default branch with a\n  `Release-As: X.Y.Z` footer (an empty commit is fine).\n- **Mistyped commit, squash-merged PR:** edit the merged PR's body to add a\n  commit override (`BEGIN_COMMIT_OVERRIDE` \u002F `END_COMMIT_OVERRIDE` around the\n  corrected message). The squash commit maps to that one PR, so the override\n  applies.\n- **Mistyped commit, plain merge commits:** the override is ignored, because\n  release-please can't tell which of the PR's commits it replaces. Add a new\n  commit on the default branch whose subject carries the correct type, e.g.\n  `git commit --allow-empty -m \"feat: add --json output flag\"`. Don't rely on\n  the override here.\n\nCheck which merge strategy the repo uses before choosing between the last two.\n\nCounter-pull: bootstrap steps (the baseline tag, the first `1.0.0`) are\ndeliberately manual.\n\n## Boundaries with sibling skills\n\n- Release workflow YAML: pinning, token permissions, runners →\n  **`ci-pipelines`**.\n- Exposing the gate as a named task → **`navigable-codebases`**.\n- What the code inside a commit looks like → **`writing-clean-code`**.\n- Out of scope: PR size and stacking, review etiquette, deploys.\n","# Commits and Releases\n\nCommit history is the input to the release: release tooling reads each commit\nsubject to pick the version bump and write the changelog. So a wrong release is\nfixed by changing that input, never the output.\n\nCommit format, breaking-change syntax, type-to-bump mapping, when to ship, and\nfixing merged history: see\n[`references\u002Frelease-please.md`](references\u002Frelease-please.md).\n\n## Releases come from history, not hand edits\n\nNever hand-edit the changelog, bump version strings or the manifest, or create\ntags that the release automation owns. That includes the files on the open\nrelease PR's branch: the next run regenerates them and your edit is lost or\ncontradicts history.\n\nFix a wrong release by changing what the tool reads:\n\n- **Wrong version:** add a commit on the default branch with a\n  `Release-As: X.Y.Z` footer (an empty commit is fine).\n- **Mistyped commit, squash-merged PR:** edit the merged PR's body to add a\n  commit override (`BEGIN_COMMIT_OVERRIDE` \u002F `END_COMMIT_OVERRIDE` around the\n  corrected message). The squash commit maps to that one PR, so the override\n  applies.\n- **Mistyped commit, plain merge commits:** the override is ignored, because\n  release-please can't tell which of the PR's commits it replaces. Add a new\n  commit on the default branch whose subject carries the correct type, e.g.\n  `git commit --allow-empty -m \"feat: add --json output flag\"`. Don't rely on\n  the override here.\n\nCheck which merge strategy the repo uses before choosing between the last two.\n\nCounter-pull: bootstrap steps (the baseline tag, the first `1.0.0`) are\ndeliberately manual.\n\n## Boundaries with sibling skills\n\n- Release workflow YAML: pinning, token permissions, runners →\n  **`ci-pipelines`**.\n- Exposing the gate as a named task → **`navigable-codebases`**.\n- What the code inside a commit looks like → **`writing-clean-code`**.\n- Out of scope: PR size and stacking, review etiquette, deploys.\n",{"name":5,"description":7},"main","f92fca73134478305fd12b6f207db4ac71a1a901","skills\u002Fcommits-and-releases","https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit","https:\u002F\u002Fgithub.com\u002Frahulmutt","2026-10-19 03:03:07",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add rahulmutt\u002Fdevkit --skill commits-and-releases",{"tool":36,"command":37},"bunx","bunx skills add rahulmutt\u002Fdevkit --skill commits-and-releases",{"tool":39,"command":40},"pnpm","pnpm dlx skills add rahulmutt\u002Fdevkit --skill commits-and-releases","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit\u002Fblob\u002Fmain\u002Fskills\u002Fcommits-and-releases\u002FSKILL.md",true,[44],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"references\u002Frelease-please.md","REFERENCE","参考文档",4085,"https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit\u002Fblob\u002Fmain\u002Fskills\u002Fcommits-and-releases\u002Freferences\u002Frelease-please.md",[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M77MEJQ0MXKQJZMXBGAXWRVZ","writing-clean-code","Use when refactoring or restructuring code, splitting a file or module that has grown too large, deciding whether to extract a helper or inline it, naming things, removing dead or unused code, drawing module or package boundaries, handling errors, writing comments, applying DDD or hexagonal (ports and adapters) architecture, or checking a language's idiomatic style.","https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-clean-code\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M77MEG5ZPHCG2VZKHV885VPQ","using-devkit","Use when starting any conversation or new engineering task in a repo with devkit installed — establishes that devkit skills exist and must be checked before acting.","https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit\u002Fblob\u002Fmain\u002Fskills\u002Fusing-devkit\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M77MECVQXHNQN0FQD62451G0","testing-practices","Use when writing, adding, or reviewing tests; choosing between unit, integration, snapshot\u002Fgolden, property, fuzz, mutation, e2e\u002FUI, or formal methods; when a test is flaky or the suite or CI is slow; or when deciding what runs in pre-commit, PR CI, or nightly.","https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit\u002Fblob\u002Fmain\u002Fskills\u002Ftesting-practices\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M77ME7KX7BK4H37744MTG2J2","security-practices","Use when code touches a trust boundary — HTTP endpoints, webhooks, file uploads, auth, sessions, permissions, SQL or shell built from input, deserialization, service-to-service calls — when handling secrets, API keys, or .env files, on a CVE or vulnerability alert, when writing a threat model, or when choosing secret, SCA, SAST, or container scanners.","https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit\u002Fblob\u002Fmain\u002Fskills\u002Fsecurity-practices\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M77ME3080TN2RA76XBGJ5WKV","navigable-codebases","Use when writing or updating a README, AGENTS.md, CLAUDE.md, GEMINI.md, ARCHITECTURE.md, or onboarding docs; when setting up a new repository; when adding or naming task-runner commands (mise tasks, Makefile, justfile, npm scripts); or when getting-started steps are missing, stale, or slow for newcomers.","https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit\u002Fblob\u002Fmain\u002Fskills\u002Fnavigable-codebases\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"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},"01M77MDZ2DRB45G9V3BTJ6VXTK","developer-environment","Use when installing or upgrading any tool, runtime, CLI, or library — brew, apt, npm i -g, pip install, cargo install, nvm, pyenv, asdf — editing mise.toml or .tool-versions, bumping or pinning versions, adding a dependency, hitting \"command not found\", setting up a dev or CI toolchain, reviewing Renovate or Dependabot version bumps, or considering Bazel.","https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit\u002Fblob\u002Fmain\u002Fskills\u002Fdeveloper-environment\u002FSKILL.md",[],[]]