[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F2DKQWCQYM09DNJ11RMA3J":3,"skill-same:01M6F2DKQWCQYM09DNJ11RMA3J":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":22,"linkOnly":23,"markdownContent":24,"markdownBody":25,"frontMatter":26,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M6F2DKQWCQYM09DNJ11RMA3J","changelog-generator",null,"Changelog Generator","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",66,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Falirezarezvani\u002Fclaude-skills\u002Fchangelog-generator\u002FSKILL.md",[],[19,20,21],"changelog","changelog generator","generator","2026-11-10 10:12:30",false,"---\nname: \"changelog-generator\"\ndescription: \"Changelog Generator\"\n---\n\n# Changelog Generator\n\n**Tier:** POWERFUL  \n**Category:** Engineering  \n**Domain:** Release Management \u002F Documentation\n\n## Overview\n\nUse this skill to produce consistent, auditable release notes from Conventional Commits. It separates commit parsing, semantic bump logic, and changelog rendering so teams can automate releases without losing editorial control.\n\n## Core Capabilities\n\n- Parse commit messages using Conventional Commit rules\n- Detect semantic bump (`major`, `minor`, `patch`) from commit stream\n- Render Keep a Changelog sections (`Added`, `Changed`, `Fixed`, etc.)\n- Generate release entries from git ranges or provided commit input\n- Enforce commit format with a dedicated linter script\n- Support CI integration via machine-readable JSON output\n\n## When to Use\n\n- Before publishing a release tag\n- During CI to generate release notes automatically\n- During PR checks to block invalid commit message formats\n- In monorepos where package changelogs require scoped filtering\n- When converting raw git history into user-facing notes\n\n## Key Workflows\n\n### 1. Generate Changelog Entry From Git\n\n```bash\npython3 scripts\u002Fgenerate_changelog.py \\\n  --from-tag v1.3.0 \\\n  --to-tag v1.4.0 \\\n  --next-version v1.4.0 \\\n  --format markdown\n```\n\n### 2. Generate Entry From stdin\u002FFile Input\n\n```bash\ngit log v1.3.0..v1.4.0 --pretty=format:'%s' | \\\n  python3 scripts\u002Fgenerate_changelog.py --next-version v1.4.0 --format markdown\n\npython3 scripts\u002Fgenerate_changelog.py --input commits.txt --next-version v1.4.0 --format json\n```\n\n### 3. Update `CHANGELOG.md`\n\n```bash\npython3 scripts\u002Fgenerate_changelog.py \\\n  --from-tag v1.3.0 \\\n  --to-tag HEAD \\\n  --next-version v1.4.0 \\\n  --write CHANGELOG.md\n```\n\n### 4. Lint Commits Before Merge\n\n```bash\npython3 scripts\u002Fcommit_linter.py --from-ref origin\u002Fmain --to-ref HEAD --strict --format text\n```\n\nOr file\u002Fstdin:\n\n```bash\npython3 scripts\u002Fcommit_linter.py --input commits.txt --strict\ncat commits.txt | python3 scripts\u002Fcommit_linter.py --format json\n```\n\n## Conventional Commit Rules\n\nSupported types:\n\n- `feat`, `fix`, `perf`, `refactor`, `docs`, `test`, `build`, `ci`, `chore`\n- `security`, `deprecated`, `remove`\n\nBreaking changes:\n\n- `type(scope)!: summary`\n- Footer\u002Fbody includes `BREAKING CHANGE:`\n\nSemVer mapping:\n\n- breaking -> `major`\n- non-breaking `feat` -> `minor`\n- all others -> `patch`\n\n## Script Interfaces\n\n- `python3 scripts\u002Fgenerate_changelog.py --help`\n  - Reads commits from git or stdin\u002F`--input`\n  - Renders markdown or JSON\n  - Optional in-place changelog prepend\n- `python3 scripts\u002Fcommit_linter.py --help`\n  - Validates commit format\n  - Returns non-zero in `--strict` mode on violations\n\n## Common Pitfalls\n\n1. Mixing merge commit messages with release commit parsing\n2. Using vague commit summaries that cannot become release notes\n3. Failing to include migration guidance for breaking changes\n4. Treating docs\u002Fchore changes as user-facing features\n5. Overwriting historical changelog sections instead of prepending\n\n## Best Practices\n\n1. Keep commits small and intent-driven.\n2. Scope commit messages (`feat(api): ...`) in multi-package repos.\n3. Enforce linter checks in PR pipelines.\n4. Review generated markdown before publishing.\n5. Tag releases only after changelog generation succeeds.\n6. Keep an `[Unreleased]` section for manual curation when needed.\n\n## References\n\n- [references\u002Fci-integration.md](references\u002Fci-integration.md)\n- [references\u002Fchangelog-formatting-guide.md](references\u002Fchangelog-formatting-guide.md)\n- [references\u002Fmonorepo-strategy.md](references\u002Fmonorepo-strategy.md)\n- [README.md](README.md)\n\n## Release Governance\n\nUse this release flow for predictability:\n\n1. Lint commit history for target release range.\n2. Generate changelog draft from commits.\n3. Manually adjust wording for customer clarity.\n4. Validate semver bump recommendation.\n5. Tag release only after changelog is approved.\n\n## Output Quality Checks\n\n- Each bullet is user-meaningful, not implementation noise.\n- Breaking changes include migration action.\n- Security fixes are isolated in `Security` section.\n- Sections with no entries are omitted.\n- Duplicate bullets across sections are removed.\n\n## CI Policy\n\n- Run `commit_linter.py --strict` on all PRs.\n- Block merge on invalid conventional commits.\n- Auto-generate draft release notes on tag push.\n- Require human approval before writing into `CHANGELOG.md` on main branch.\n\n## Monorepo Guidance\n\n- Prefer commit scopes aligned to package names.\n- Filter commit stream by scope for package-specific releases.\n- Keep infra-wide changes in root changelog.\n- Store package changelogs near package roots for ownership clarity.\n\n## Failure Handling\n\n- If no valid conventional commits found: fail early, do not generate misleading empty notes.\n- If git range invalid: surface explicit range in error output.\n- If write target missing: create safe changelog header scaffolding.\n\n","# Changelog Generator\n\n**Tier:** POWERFUL  \n**Category:** Engineering  \n**Domain:** Release Management \u002F Documentation\n\n## Overview\n\nUse this skill to produce consistent, auditable release notes from Conventional Commits. It separates commit parsing, semantic bump logic, and changelog rendering so teams can automate releases without losing editorial control.\n\n## Core Capabilities\n\n- Parse commit messages using Conventional Commit rules\n- Detect semantic bump (`major`, `minor`, `patch`) from commit stream\n- Render Keep a Changelog sections (`Added`, `Changed`, `Fixed`, etc.)\n- Generate release entries from git ranges or provided commit input\n- Enforce commit format with a dedicated linter script\n- Support CI integration via machine-readable JSON output\n\n## When to Use\n\n- Before publishing a release tag\n- During CI to generate release notes automatically\n- During PR checks to block invalid commit message formats\n- In monorepos where package changelogs require scoped filtering\n- When converting raw git history into user-facing notes\n\n## Key Workflows\n\n### 1. Generate Changelog Entry From Git\n\n```bash\npython3 scripts\u002Fgenerate_changelog.py \\\n  --from-tag v1.3.0 \\\n  --to-tag v1.4.0 \\\n  --next-version v1.4.0 \\\n  --format markdown\n```\n\n### 2. Generate Entry From stdin\u002FFile Input\n\n```bash\ngit log v1.3.0..v1.4.0 --pretty=format:'%s' | \\\n  python3 scripts\u002Fgenerate_changelog.py --next-version v1.4.0 --format markdown\n\npython3 scripts\u002Fgenerate_changelog.py --input commits.txt --next-version v1.4.0 --format json\n```\n\n### 3. Update `CHANGELOG.md`\n\n```bash\npython3 scripts\u002Fgenerate_changelog.py \\\n  --from-tag v1.3.0 \\\n  --to-tag HEAD \\\n  --next-version v1.4.0 \\\n  --write CHANGELOG.md\n```\n\n### 4. Lint Commits Before Merge\n\n```bash\npython3 scripts\u002Fcommit_linter.py --from-ref origin\u002Fmain --to-ref HEAD --strict --format text\n```\n\nOr file\u002Fstdin:\n\n```bash\npython3 scripts\u002Fcommit_linter.py --input commits.txt --strict\ncat commits.txt | python3 scripts\u002Fcommit_linter.py --format json\n```\n\n## Conventional Commit Rules\n\nSupported types:\n\n- `feat`, `fix`, `perf`, `refactor`, `docs`, `test`, `build`, `ci`, `chore`\n- `security`, `deprecated`, `remove`\n\nBreaking changes:\n\n- `type(scope)!: summary`\n- Footer\u002Fbody includes `BREAKING CHANGE:`\n\nSemVer mapping:\n\n- breaking -> `major`\n- non-breaking `feat` -> `minor`\n- all others -> `patch`\n\n## Script Interfaces\n\n- `python3 scripts\u002Fgenerate_changelog.py --help`\n  - Reads commits from git or stdin\u002F`--input`\n  - Renders markdown or JSON\n  - Optional in-place changelog prepend\n- `python3 scripts\u002Fcommit_linter.py --help`\n  - Validates commit format\n  - Returns non-zero in `--strict` mode on violations\n\n## Common Pitfalls\n\n1. Mixing merge commit messages with release commit parsing\n2. Using vague commit summaries that cannot become release notes\n3. Failing to include migration guidance for breaking changes\n4. Treating docs\u002Fchore changes as user-facing features\n5. Overwriting historical changelog sections instead of prepending\n\n## Best Practices\n\n1. Keep commits small and intent-driven.\n2. Scope commit messages (`feat(api): ...`) in multi-package repos.\n3. Enforce linter checks in PR pipelines.\n4. Review generated markdown before publishing.\n5. Tag releases only after changelog generation succeeds.\n6. Keep an `[Unreleased]` section for manual curation when needed.\n\n## References\n\n- [references\u002Fci-integration.md](references\u002Fci-integration.md)\n- [references\u002Fchangelog-formatting-guide.md](references\u002Fchangelog-formatting-guide.md)\n- [references\u002Fmonorepo-strategy.md](references\u002Fmonorepo-strategy.md)\n- [README.md](README.md)\n\n## Release Governance\n\nUse this release flow for predictability:\n\n1. Lint commit history for target release range.\n2. Generate changelog draft from commits.\n3. Manually adjust wording for customer clarity.\n4. Validate semver bump recommendation.\n5. Tag release only after changelog is approved.\n\n## Output Quality Checks\n\n- Each bullet is user-meaningful, not implementation noise.\n- Breaking changes include migration action.\n- Security fixes are isolated in `Security` section.\n- Sections with no entries are omitted.\n- Duplicate bullets across sections are removed.\n\n## CI Policy\n\n- Run `commit_linter.py --strict` on all PRs.\n- Block merge on invalid conventional commits.\n- Auto-generate draft release notes on tag push.\n- Require human approval before writing into `CHANGELOG.md` on main branch.\n\n## Monorepo Guidance\n\n- Prefer commit scopes aligned to package names.\n- Filter commit stream by scope for package-specific releases.\n- Keep infra-wide changes in root changelog.\n- Store package changelogs near package roots for ownership clarity.\n\n## Failure Handling\n\n- If no valid conventional commits found: fail early, do not generate misleading empty notes.\n- If git range invalid: surface explicit range in error output.\n- If write target missing: create safe changelog header scaffolding.\n\n",{"name":5,"description":7},"main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Falirezarezvani\u002Fclaude-skills\u002Fchangelog-generator",24,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub","https:\u002F\u002Fskillshub.wtf","https:\u002F\u002Fgithub.com\u002FComeOnOliver","AI & Blockchain Engineer\r\n","2026-06-24 22:07:19",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill changelog-generator",{"tool":42,"command":43},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill changelog-generator",{"tool":45,"command":46},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill changelog-generator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Falirezarezvani\u002Fclaude-skills\u002Fchangelog-generator\u002FSKILL.md",true,[],[51,65,75,84,90,97],{"skillNo":52,"name":53,"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":54,"categories":55,"keywords":61,"publishedAt":22},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[56],{"categoryNo":57,"categoryName":58,"taxonomyType":59,"taxonomyTypeDesc":60},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[62,63,64],"model","model hierarchy","model hierarchy skill",{"skillNo":66,"name":67,"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":68,"categories":69,"keywords":71,"publishedAt":22},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[70],{"categoryNo":57,"categoryName":58,"taxonomyType":59,"taxonomyTypeDesc":60},[72,73,74],"MCP","zoom","zoom mcp",{"skillNo":76,"name":77,"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":78,"categories":79,"keywords":80,"publishedAt":22},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[81,82,83,73],"sdk","zoom apps sdk","apps",{"skillNo":85,"name":86,"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":87,"categories":88,"keywords":89,"publishedAt":22},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[86],{"skillNo":91,"name":92,"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":93,"categories":94,"keywords":96,"publishedAt":22},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[95],{"categoryNo":57,"categoryName":58,"taxonomyType":59,"taxonomyTypeDesc":60},[92],{"skillNo":98,"name":99,"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":100,"categories":101,"keywords":102,"publishedAt":22},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[99]]