skills.rest
nullhack
nullhackCOMMUNITY
Explore all skills by this author →
GitHub

pr-management

Automate pull request creation and management with conventional commits.

Updated Apr 17, 2026
Search Tags:#automation#git#workflow#branching#pr#pull-request#conventional-commits
One-click install
npx skills add https://github.com/nullhack/pytest-beehave --skill pr-management-nullhack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-management
Source: https://github.com/nullhack/pytest-beehave/tree/main/.opencode/skills/pr-management
Command: npx skills add https://github.com/nullhack/pytest-beehave --skill pr-management-nullhack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and manage pull requests after a reviewer approves the feature, enforcing conventional commits, proper formatting, and a clean branch workflow to keep code changes auditable and reviewable.

Core Features & Use Cases

  • Branch naming guidelines reflect feature work and fixes (e.g., feature/<name>, fix/<description>, chore/<scope>).
  • Conventional commits formatting examples to standardize messaging: feat, fix, docs, chore, etc.
  • PR creation workflow with a ready-to-use PR body template and checks to ensure acceptance criteria are captured.

Quick Start

Push your feature branch and run the PR creation sequence to open a well-structured pull request.

Frequently Asked Questions about pr-management

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

FAQPage Schema
How do I automate pull request creation with conventional commits?▼

Conventional commits standardize pull request messaging by enforcing specific prefixes like feat, fix, docs, and chore, ensuring code changes remain auditable and reviewable across software teams.

What is the correct branch naming workflow for feature development and fixes?▼

The correct branch naming workflow for feature development and fixes uses prefixes reflecting the work type, such as feature/<name> for new features, fix/<description> for bug fixes, and chore/<scope> for maintenance tasks.

How do I generate a PR body template that captures acceptance criteria?▼

You generate a PR body template that captures acceptance criteria by running the automated PR creation workflow, which provides a ready-to-use template and runs pre-creation checks to ensure all criteria are documented.

Can I use this PR workflow to enforce commit message formatting before opening a pull request?▼

Yes, you can use this PR workflow to enforce commit message formatting before opening a pull request through built-in pre-creation checklists that validate conventional commit conventions and proper branch naming.

What's the best way to keep code changes auditable and reviewable after feature approval?▼

The best way to keep code changes auditable and reviewable after feature approval is to automate PR management with standardized conventional commits, strict branch naming guidelines, and structured PR body templates.

Related Skills

Explore More Software Engineering Skills→
ether-moonether-moon

managing-git-workflow

Automate git commits, pushes, and pull request creation for local GitHub repositories.

Community
Advanced
hirokimryhirokimry
1

knowledge-pr

Convert knowledge buffer changes into GitHub issues and pull requests with CI gating.

Community
Advanced
JackSmack1971JackSmack1971

git-commit-standards

Configure pre-commit hooks to validate conventional commit messages.

Community
Intermediate
GolferGeekGolferGeek

GitHub Workflow

Standardize GitHub branching, pull requests, code reviews, and CI/CD pipelines.

Community
Basic