ad-pr

Open GitHub pull requests with an ADR-0024 structured body.

728|16|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime --skill ad-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ad-pr
Source: https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime/tree/main/.agents/skills/ad-pr
Command: npx skills add https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime --skill ad-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open PRs with a uniform body shape across ADR-0024, reducing manual drafting and ensuring consistent reviews.

Core Features & Use Cases

  • Opens PRs with a standardized 4-phase body (preflight, scope, draft, links) and computes a clean title from commits.
  • Generates back-links to ADRs, tasks, and issues to improve traceability.
  • Works with gh CLI to create PRs directly from your branch for automated workflows.

Quick Start

Prepare a standardized PR draft and create the PR using gh pr create.

Frequently Asked Questions about ad-pr

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

FAQPage Schema
How do I create a GitHub pull request with a consistent body template?

To create a GitHub pull request with a consistent body, you can use automation to generate a standardized draft. This ensures your PR includes a uniform summary, test plan, and links, reducing manual formatting effort.

How do I automate preflight checks before opening a PR with gh CLI?

Automating preflight checks before opening a PR with gh CLI involves running validation scripts on your feature branch. This verifies code readiness and ensures the branch meets all requirements before the pull request is created.

Can I automatically derive a PR title from my git commits?

Yes, you can automatically derive a PR title from your git commits. The automation computes a clean title from your commit history, ensuring the pull request header accurately reflects the branch changes.

How do I generate back-links to ADRs and issues in a pull request?

To generate back-links to ADRs and issues in a pull request, the automation adds a dedicated links section to the PR body. This improves traceability by connecting your code changes directly to relevant tasks and architecture decisions.

What is the best way to standardize pull request narratives across a team?

The best way to standardize pull request narratives is applying a structured PR body format like ADR-0024. This enforces a 4-phase draft including preflight, scope summary, and linked references for consistent reviews.

Do I need the gh CLI to automate PR creation?

Yes, you need the gh CLI to automate PR creation directly from your branch. The tool leverages the GitHub command line interface to execute preflight validations and run the PR creation command.