skills.rest
lleontor705
lleontor705COMMUNITY
Explore all skills by this author →
WebsiteGitHub

open-pr

Enforce issue-first governance and type labels on GitHub pull requests.

1|Updated Mar 30, 2026
Search Tags:#github-actions#code-review#pull-request#conventional-commits#branch-naming#issue-linking#pr-workflow
One-click install
npx skills add https://github.com/lleontor705/cortex-ia --skill open-pr-lleontor705
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: open-pr
Source: https://github.com/lleontor705/cortex-ia/tree/main/internal/assets/skills/open-pr
Command: npx skills add https://github.com/lleontor705/cortex-ia --skill open-pr-lleontor705

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically enforces issue-first governance on GitHub pull requests by ensuring every PR links an approved issue and carries exactly one type label.

Core Features & Use Cases

  • Enforces linking an approved issue via Closes/Fixes/Resolves references.
  • Requires exactly one type label and validates branch naming and commit message formats.
  • Applies the PR body template and returns the PR URL to the caller for tracking.
  • Useful in teams adopting strict PR governance and automated checks.

Quick Start

Create a PR that links an approved issue, uses exactly one type label, and follows the branch and commit conventions.

Frequently Asked Questions about open-pr

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

FAQPage Schema
How do I enforce issue-first linking on GitHub pull requests?▼

Enforcing issue-first linking on GitHub pull requests requires a governance check that validates Closes, Fixes, or Resolves references to approved issues before a PR can proceed. This ensures every change traces back to an approved issue.

How do I require exactly one type label on a pull request?▼

Requiring exactly one type label on a pull request involves applying an automated governance rule that checks PR labels and rejects submissions carrying zero or multiple type labels. This standardizes PR categorization across your repository.

Can I validate conventional commits and branch naming in a GitHub Actions PR workflow?▼

Yes, validating conventional commits and branch naming in a GitHub Actions PR workflow is possible by applying automated checks that enforce type/description patterns for branches and commit messages. This standardizes PR bodies and governance.

What is the best way to automate pull request governance for strict code review workflows?▼

Automating pull request governance for strict code review workflows is best achieved by implementing checks that enforce issue-first linking, single type labels, and conventional commit formats. This returns the created PR URL to the caller for tracking.

Do I need an approved issue before creating a pull request with automated governance?▼

Yes, an approved issue is required before creating a pull request with automated governance because issue-first enforcement requires a valid Closes, Fixes, or Resolves reference. Without an approved linked issue, the PR governance check will fail.

Related Skills

Explore More Software Engineering Skills→
Nick777-PixelNick777-Pixel

linear

Automate Linear issue status updates and completion comments from PR references.

Community
Advanced
JeffallanJeffallan
10.9k

Code Reviewer

Automate pull request reviews for code quality, security, and maintainability.

Community
Basic
tachfineamnaytachfineamnay

Git Workflow & CI/CD

Standardize Git workflows and CI/CD pipelines with Husky and GitHub Actions.

Community
Intermediate
RyoMurakami1983RyoMurakami1983
2

git-initial-setup

Automates GitLab project and repository setup for streamlined onboarding and management.

Community
Intermediate