Claude skills for Dev Workflow

4 skills in the bank are filed under Dev Workflow. They are grouped here because they compete for the same jobs — which is the reason an agent reaching for one of them sometimes gets another.

• Conventional CommitmarcelorodrigoShapes the message of the commit you are about to make into the Conventional Commits format — a `type(scope): subject` header with an optional body, footer, and breaking-change marker that downstream tooling can parse. Its job is WORDING one commit; it does not rewrite past history, juggle branches, or assemble the release those commits eventually roll into.
• Create Pull RequestclineTurns a finished feature branch into a review-ready GitHub pull request — confirming the branch and base, summarising the commits into a description, filling the repo's PR template, and opening it with the `gh` CLI. It is about PUBLISHING your own work for review, not judging someone else's PR, crafting the individual commits, or tagging the release that follows.
• Git Advanced WorkflowswshobsonReshapes an existing Git history and untangles branches — interactive rebase, cherry-picking, bisecting to the commit that broke something, worktrees, and rescuing lost work through the reflog. It is about MANIPULATING the repository's history and recovering from mistakes, not about how you word a commit, open a pull request, or cut a release.
• Release SkillsjimliuCuts a versioned release for whatever kind of project you have — detecting the version file (package.json, pyproject.toml, Cargo.toml, and more), bumping the semantic version, updating the changelog, tagging, and publishing a GitHub Release. It handles SHIPPING the release, not the branch surgery, commit wording, or pull-request creation that comes before it.