git-trunk-based-workflow
Git Trunk-Based Workflow
Guide contributors through a safe trunk-based Git workflow.
Goal
Keep main releasable while integrating small changes frequently and predictably.
Canonical rules table
Use this table as the single source of truth for workflow decisions.
More from octivi/skills
common-changelog
Draft and normalize user-facing CHANGELOG.md entries in Common Changelog format from release notes, pull requests, and Conventional Commits (including git trailers like Category, Ref, and Co-authored-by). Use this skill whenever the user asks for changelog text, release notes, "what changed", version summaries, or Unreleased notes, even if they do not explicitly mention CHANGELOG.md.
9git-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