version-control

Create issue-linked git branches, commits, and pull requests via GitHub CLI.

Updated Mar 2, 2022
One-click install
npx skills add https://github.com/ysuurme/azure_hello_world --skill version-control-ysuurme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-control
Source: https://github.com/ysuurme/azure_hello_world/tree/main/.agents/skills/version-control
Command: npx skills add https://github.com/ysuurme/azure_hello_world --skill version-control-ysuurme

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about version-control

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub pull requests that close issues with standardized branch naming?

You can automate issue-linked pull requests by enforcing feature/fix/docs/refactor branch naming conventions, generating formatted commit messages, and using GitHub CLI patterns to open PRs containing `Closes #N` to auto-close the referenced issue.

What commit message format ensures proper issue traceability when automating git workflows?

Proper issue traceability requires commit messages formatted as `<type>(<scope>): <description>`, with the final commit including `Closes #N` to link the commit to the specific GitHub Issue and ensure automated closure upon PR merge.

How do I create a git branch from a GitHub Issue number with consistent naming conventions?

Branch creation from a GitHub Issue uses the issue number and a dense kebab-case slug to generate standardized branch names like `feature/42-<slug>`, ensuring full traceability from issue to branch to pull request.

Can I use git worktrees to manage isolated fix branches without polluting my main working directory?

Yes, git worktrees can be used to handle isolated fix branches, allowing you to work on separate feature or fix branches simultaneously without polluting the main working directory or disrupting your primary git workflow.

Does this version control workflow require the GitHub CLI to open issue-linked pull requests?

Yes, the workflow relies on GitHub CLI patterns to automate opening pull requests whose title and body include `Closes #N`, ensuring the branch, commits, and PR are properly linked to the original GitHub Issue.