mp-gh-issue-branch-pr

To convert local changes into a GitHub issue and draft PR, this Skill captures your current Git status and diffs to draft a labeled issue, creates a matching branch, commits using conventional commits, and opens a draft PR with Closes linkage. It automates the entire issue-first workflow.

Yes, you can create an issue-driven branch and pull request using existing repository labels. The workflow matches your current changes to existing labels like bug, feature, chore, or docs without creating new labels, ensuring the generated issue and PR align with your repository's established categorization.

The best way to automate conventional commits and GitHub PR linkage is using an issue-first workflow that stages specific files, commits with conventional format, detects the base branch, and adds Resolves or Closes linkage to a draft PR, ensuring proper traceability from issue to merge.

Yes, this workflow requires the gh CLI to create branches and pull requests. The process relies on Git commands and gh CLI usage to capture local context, create the GitHub issue, push the derived branch, and establish the draft PR with proper issue linkage.

Your automated pull request needs a Closes linkage to a GitHub issue to automatically close the issue upon merging. This issue-driven workflow extracts the issue number from the branch metadata and injects the linkage into the draft PR description, maintaining clean project tracking.

To handle base branch detection when creating a draft PR, the workflow automatically identifies the appropriate base branch in your repository. It then creates or updates the draft PR targeting that branch, ensuring your conventional commit changes merge into the correct integration line.