Enforce issue linking, branch naming, and label validation for pull requests.
npx skills add https://github.com/aroca89/roca_teams --skill branch-pr-aroca89
Please help me install this Agent Skill. Skill: branch-pr Source: https://github.com/aroca89/roca_teams/tree/main/skills/branch-pr Command: npx skills add https://github.com/aroca89/roca_teams --skill branch-pr-aroca89
This workflow prevents roca_teams contributors from submitting pull requests without an approved issue, clear branch naming, or passing automated checks, eliminating common review bottlenecks. It avoids chaotic context by enforcing a deterministic approval, labeling, and validation path before any code is merged.
status:approved, keeping approvals and scope aligned.type/description naming, a single type:* label, conventional commit messages, and shellcheck plus CI validations.Prepare your branch as type/description, link the approved issue, and open the PR using the branch-pr workflow before running shellcheck.
High-intent search queries and answers about installing and using this skill.
To enforce an issue-first pull request workflow, link every PR to an approved issue, use type/description branch naming, apply a single type:* label, and run conventional commit checks before merging.
The required branch naming format for compliant pull request creation is type/description, ensuring every feature or fix branch follows a deterministic structure before opening a pull request.
Yes, you need an approved issue before opening a pull request. The workflow enforces issue linking by requiring every PR to reference an issue labeled status:approved.
To validate conventional commit messages and shellcheck before merging a PR, the workflow enforces automated check prerequisites, ensuring commit format and shell scripts pass CI validations.
No, you cannot apply multiple type labels to a pull request using this workflow. It enforces single type:* label guardrails to prevent chaotic context and maintain clear review scope.
The limitations of enforcing automated check prerequisites include strict dependency on passing shellcheck and conventional commit validations, which blocks PR merging if any automated check fails.
jandragsbaekCreate feature branches, rebase onto main, and open GitHub PRs with labels.
softsparkCreate GitHub pull requests with pre-flight validation and automated commit summaries.
jim60105Automate GitHub issue implementation into branching, testing, and pull requests.
YoshikemoloGenerate Git branch names and validate commit messages against Jira issues.