common-changelog
Common Changelog
Write human-facing changelog entries in Common Changelog format.
When to use
Use this skill when asked to generate, update, or normalize CHANGELOG.md from commits, PRs, or
release notes.
When not to use
- Do not use for commit message wording; route to
git-commits. - Do not use for branch/rebase/PR process guidance; route to
git-trunk-based-workflow.
Goal
Help readers answer: what changed and how it affects them.
Output contract
More from octivi/skills
git-trunk-based-workflow
Plan and execute Git Trunk-Based Development workflows on a repository with main as trunk. Use whenever the user asks about branch strategy, branch naming, rebasing on main, merge conflicts during rebase, PR flow, merge strategy, safe history rewrite, or branch cleanup, even if they do not mention "trunk-based" explicitly. For commit message formatting and Conventional Commits wording, delegate to git-commits.
10git-commits
Draft, rewrite, and review Git commit messages using Conventional Commits and commit hygiene rules. Use whenever the user asks for commit text, commit message fixes, type/scope selection, breaking-change notation, trailers (for example See or Co-authored-by), splitting work into atomic commits, or commit readiness before a PR, even if they ask in informal terms like "polish this commit message".
5