skills.rest
CarlosWilliamsR
CarlosWilliamsRCOMMUNITY
Explore all skills by this author →
GitHub

branch-pr

Creates GitHub pull requests with issue linkage, branch naming rules, and conventional commits.

Updated Aug 25, 2026
Search Tags:#code review#pull request#conventional commits#github#shellcheck#branch naming#ci validation
One-click install
npx skills add https://github.com/CarlosWilliamsR/SketchOS --skill branch-pr-carloswilliamsr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch-pr
Source: https://github.com/CarlosWilliamsR/SketchOS/tree/main/.config/opencode/skills/branch-pr
Command: npx skills add https://github.com/CarlosWilliamsR/SketchOS --skill branch-pr-carloswilliamsr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Contributors often open pull requests that lack linked issues, proper labels, or valid branch names, causing automated checks to fail and blocking merges. This Skill enforces the Gentle AI repository's PR workflow so every submission passes validation on the first attempt. ## Core Features & Use Cases - Issue-First Validation: Verifies the linked issue carries the status:approved label before any PR is opened, preventing blocked submissions. - Branch Naming Enforcement: Applies the type/description regex convention (feat, fix, chore, docs, and more) so branch names pass CI validation. - Conventional Commits & Labels: Maps commit types like feat(scope): description to the required type:* PR labels, including breaking-change detection. - Use Case: A contributor fixing a shell script bug uses this Skill to create the branch fix/zsh-glob-error, run shellcheck, open a PR with Closes #42, and add the type:bug label so all GitHub Actions checks pass. ## Quick Start Ask the agent to create a pull request for issue number 42 following the repository's branch naming and labeling rules.

Frequently Asked Questions about branch-pr

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

FAQPage Schema
How do I create a pull request that passes GitHub Actions validation?▼

Link an approved issue using Closes #N in the PR body, add exactly one type:* label, and ensure shellcheck passes on modified scripts. The PR Validation workflow checks the issue reference, its status:approved label, and the PR label before merge is allowed.

What branch naming convention should I use for pull requests?▼

Use the format type/description, such as feat/user-login or fix/zsh-glob-error. The type must be one of feat, fix, chore, docs, style, refactor, perf, test, build, ci, or revert, and the description must be lowercase using only a-z, 0-9, dots, underscores, and hyphens.

How do conventional commit messages map to PR labels?▼

Each commit type maps to a label: feat becomes type:feature, fix becomes type:bug, docs becomes type:docs, and refactor becomes type:refactor. Breaking changes marked with an exclamation like feat! map to type:breaking-change.

Why was my pull request blocked by GitHub Actions?▼

PRs are blocked when the body lacks a Closes, Fixes, or Resolves issue reference, the linked issue is missing the status:approved label, or the PR has zero or multiple type:* labels. Blank PRs without issue linkage are always rejected.

Can I open a pull request without a linked issue?▼

No. Every PR must link an approved issue with no exceptions. The Check Issue Reference and Check Issue Has status:approved jobs in the PR Validation workflow will fail and block merging until a valid issue is linked.

Related Skills

Explore More Software Engineering Skills→
etrigan16etrigan16

issue-creation

Creates GitHub issues using bug report and feature request templates with label workflows.

Community
Intermediate
bitpantrybitpantry

finish-pr

Merge reviewed GitHub pull requests after tests pass and branches sync.

Community
Advanced
d-oitd-oit
13

shell-script-quality

Lint shell scripts with ShellCheck and run BATS test suites.

Community
Intermediate
jbabin91jbabin91
5

git-workflow

Design Git workflows and CI/CD patterns with branching models and conventional commits.

Community
Advanced