skills.rest
michael-conrad
michael-conradCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pr-creation-workflow

Enforce PR authorization, branch targeting, and changelog generation before creation.

Updated Apr 24, 2026
Search Tags:#workflow#changelog#authorization#review#branch#pr#pull-request
One-click install
npx skills add https://github.com/michael-conrad/.opencode --skill pr-creation-workflow-michael-conrad
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-creation-workflow
Source: https://github.com/michael-conrad/.opencode/tree/main/skills/pr-creation-workflow
Command: npx skills add https://github.com/michael-conrad/.opencode --skill pr-creation-workflow-michael-conrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR authorization and governance for code changes. It ensures every PR is intentional, authorized, and properly scoped before creation.

Core Features & Use Cases

  • Enforces explicit PR authorization scope before creation
  • Verifies PR readiness, changelog generation, and branch targeting
  • Generates standardized PR bodies and strategy guidance for releases

Quick Start

Provide explicit PR authorization, prepare PR body text, and verify scope before submitting the PR.

Frequently Asked Questions about pr-creation-workflow

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

FAQPage Schema
How do I enforce PR authorization and branch targeting before creating a pull request?▼

PR authorization is enforced by verifying explicit scope, branch targeting, and changelog readiness before PR creation. This ensures every pull request is intentional, authorized, and properly scoped rather than submitted ad hoc.

What is the best way to generate standardized PR bodies for release workflows?▼

Standardized PR bodies for releases are generated by applying strategy guidance and readiness checks during PR body preparation. This produces consistent, traceable pull request descriptions aligned with your release workflow.

How do I verify PR readiness and scope before submitting a pull request?▼

PR readiness is verified by checking explicit authorization scope, branch targeting, and changelog generation before submission. These checks confirm the pull request is deliberate and properly scoped for the target branch.

Can I apply PR governance checks across both feature and release workflows?▼

PR governance checks apply across both feature and release workflows. The authorization and readiness process ensures PR creation, strategy, and body preparation are consistent regardless of workflow type.

Why does my pull request need explicit authorization before creation?▼

Explicit PR authorization is needed to ensure every pull request is intentional and properly scoped before creation. Without it, changes risk being untraceable or misaligned with the target branch and release strategy.

Related Skills

Explore More Software Engineering Skills→
yamato0811yamato0811

pull-request-creator

Summarize Git branch diffs and draft a pull request targeting develop.

Community
Basic
coco-researchcoco-research
264

gsd-ship

Push a verified branch and create a merge-ready pull request.

Community
Advanced
dseirz-rgbdseirz-rgb

git-workflow

Standardize Git workflows with Conventional Commits and branch naming conventions.

Community
Basic
wagnerra23wagnerra23

pr-ui-judge-manual

Evaluate GitHub pull request UI quality against Constituição UI v2.

Community
Advanced