skills.rest
jibaxZZZ
jibaxZZZCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pr-helper

Format pull request titles and summaries with conventional commit styles.

Updated Dec 25, 2025
Search Tags:#workflow#code-review#pull-request#conventional-commit#change-summary#pr-quality
One-click install
npx skills add https://github.com/jibaxZZZ/codex-root-configuration --skill pr-helper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-helper
Source: https://github.com/jibaxZZZ/codex-root-configuration/tree/main/.codex/skills/pr-helper
Command: npx skills add https://github.com/jibaxZZZ/codex-root-configuration --skill pr-helper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline PRs by formatting titles to conventional commit styles and generating clear, review-ready summaries for changes.

Core Features & Use Cases

  • Format PR titles to match conventional commits (feat, fix, docs, etc.)
  • Generate concise change summaries and highlight risks
  • Include a STATUS block when tests are run and pass
  • Provide a ready-to-review checklist for reviewers

Quick Start

Summarize the changes and generate a conventional-commit title for the PR.

Frequently Asked Questions about pr-helper

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

FAQPage Schema
How do I format a pull request title to match conventional commit styles?▼

Conventional commit titles are formatted by enforcing prefixes like feat, fix, or docs to standardize pull request changes. This ensures code review consistency and clear change summaries across software development workflows.

What is the best way to generate a clear change summary for a pull request?▼

Generating a clear change summary involves extracting concise descriptions of code changes and highlighting potential risks. This provides a review-ready pull request body with descriptive context for code reviewers.

How do I add a reviewer checklist to my pull request automatically?▼

A ready-to-review checklist is generated automatically to validate tests and lints within the pull request workflow. This enforces PR quality by providing reviewers with a standardized verification list.

Can I include test and lint status blocks in my pull request descriptions?▼

A STATUS block is included when tests are run and pass during pull request creation. This validates tests and lints directly within the PR body to streamline the code review process.

Does this PR formatting tool work for both bug fixes and feature work?▼

PR formatting applies to software development workflows requiring standardized commits across code changes, bug fixes, and feature work. It enforces conventional-commit style and validates tests for diverse development scenarios.

Related Skills

Explore More Software Engineering Skills→
s205109s205109
2

cck-verify

Verify .NET solution builds, tests, formatting, and git status before commits.

Community
Intermediate
taloncjonestaloncjones

ship

Automate code review, testing, version bump, merge, and post-merge cleanup for pull requests.

Community
Advanced
aniruddh2003aniruddh2003
1

speckit.checker

Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.

Community
Intermediate
mvillmowmvillmow
18

generate-changelog

Generate a Markdown changelog from git commits grouped by conventional commit types.

Community
Basic