What problem does it solve?
This Skill prevents broken traceability and inconsistent git hygiene by enforcing a single, repeatable workflow for turning a GitHub Issue into a correctly named branch, well-formatted commits, and an issue-linked pull request.
Core Features & Use Cases
- Issue-to-branch traceability: Creates branches that follow the required pattern using the GitHub Issue number and a dense kebab-case slug.
- Consistent commit conventions: Generates commit messages in the required
<type>(<scope>): <description> format and ensures the final commit includes Closes #N.
- Issue-linked PR automation: Uses GitHub CLI patterns to open a PR whose title/body include
Closes #N and supports the full branch→commit→PR flow.
- Isolated fix workflows: Optionally uses git worktrees to handle isolated fix branches without polluting the main working directory.
Example use case: An agent completes changes for GitHub Issue #42; this Skill ensures the branch is named feature/42-<slug>, the final commit includes Closes #42, and the PR body also contains Closes #42 so the issue is auto-closed.
Quick Start
Use the version-control skill to create a feature branch for GitHub Issue 42, commit your changes with the required convention, and open a PR whose body includes Closes #42.