branchThis skill should be used when the user asks to "create a branch", "new branch", "start a new branch", "branch off", "branch for this", "move this work to a new branch", "put these changes on their own branch", or "/branch" — and whenever a branch must be created before starting new development. Run
commitThis skill should be used when the user asks to "commit", "commit these changes", "create a commit", "stage and commit", or "/commit", and wants one or more git commits created following Conventional Commits. Never pushes to a remote.
conventional-commitsThis skill should be used whenever the wording/formatting of a commit message itself is the task — writing one from a diff or description, formatting one as Conventional Commits, checking what type/scope/breaking-change marker to use, or another skill (such as the sibling `commit` skill in this plug
pr-descriptionThis skill should be used by a hosting-specific pull/merge request skill (such as the `github` plugin's `pr` skill, or an equivalent for GitLab/Bitbucket) whenever it needs to derive a Conventional Commits title and a description for a whole branch. It is vendor-agnostic — it never talks to a host A