pr

Run discovered tests and generate a pull request with a changelog.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/bc05/codex-skills --skill pr-bc05
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/bc05/codex-skills/tree/main/pr
Command: npx skills add https://github.com/bc05/codex-skills --skill pr-bc05

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end PR workflow, ensuring that a branch is transformed into a reviewable pull request with local validation before submission.

Core Features & Use Cases

  • Validated PRs: Run all discovered tests locally and block submission if any fail.
  • Clear Communication: Generate a descriptive PR title and a complete changelog for reviewers.
  • Review Readiness: Provide guidance for reviewers with a deterministic workflow and change summary.

Quick Start

Run all tests locally, then open a PR with a descriptive title and a complete changelog.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate git pull request workflows with local tests?

Automating git pull request workflows involves running discovered tests locally, blocking submission on failures, and generating a review-ready PR with a descriptive title and changelog. This validates branch changes before opening a review.

What is the best way to generate a changelog for code review?

Generating a changelog for code review is best handled by summarizing branch changes into a comprehensive PR body. This provides reviewers with a deterministic workflow and clear change summary.

Can I block pull request submission if local tests fail?

You can block pull request submission if local tests fail by validating all discovered tests locally first. The workflow ensures no PR is opened until the test suite passes successfully.

How do I prepare a review-ready PR with a descriptive title?

Preparing a review-ready PR requires composing a descriptive title and a complete changelog. This transforms a local development branch into a structured submission ready for reviewer feedback.

Does automated PR generation work with existing local development workflows?

Automated PR generation works directly with local development workflows where tests must pass before submission. It applies deterministic validation to branch changes before opening a pull request.