forge-pr

Generate PR titles and narrative bodies from code changes.

25|2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/srid/agency --skill forge-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-pr
Source: https://github.com/srid/agency/tree/main/.apm/skills/forge-pr
Command: npx skills add https://github.com/srid/agency --skill forge-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve?

Write PR titles and bodies that grab attention and clarify change intent, reducing review cycles and back-and-forth.

## Core Features & Use Cases

  • Automatic generation of concise, outcome-focused PR titles that summarize the change.
  • Narrative PR bodies that explain the “why” and impact, not just the diff.
  • Cross-forge support (GitHub today; Bitbucket planned) for both new PRs and PR updates, with clear formatting and emphasis.

### Quick Start

Describe the change succinctly and ask forge-pr to produce a compelling title and narrative body for the PR.

Frequently Asked Questions about forge-pr

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

FAQPage Schema
How do I write a good pull request title and body from a git diff?

Pull request writing generates concise, outcome-focused titles and narrative bodies directly from your code diff. It explains the change intent and impact, reducing review cycles and back-and-forth by emphasizing the why rather than just the code changes.

What is the best way to automate PR writing for GitHub repositories?

Automating PR writing for GitHub generates compelling titles and narrative descriptions aligned with your project goals. It applies engaging tone, avoids boilerplate, and uses bold and italics formatting to clarify change intent across diverse repositories.

Can I use this to update existing pull requests, or does it only create new ones?

This PR writing tool supports both new PR creation and PR updates. It generates narrative descriptions and titles for code changes across forge contexts, ensuring the updated body aligns with the underlying diff and avoids generic boilerplate.

Does this PR writing tool work with platforms other than GitHub?

This tool currently supports GitHub PR generation and cross-forge contexts, with Bitbucket support planned. It aligns PR titles and narrative bodies with the underlying diff across diverse repositories.

How do I avoid boilerplate text in code review descriptions?

Avoiding boilerplate in code review descriptions requires generating narrative PR bodies that explain the why and impact. This tool formats text with bold and italics emphasis to produce engaging, outcome-focused communication instead of generic summaries.

Why should I use a narrative format for pull request bodies instead of just listing the diff?

Using a narrative format for PR bodies clarifies change intent and impact, which listing a raw diff cannot do. This approach reduces review cycles and back-and-forth by explaining the why behind the code changes and aligning with project goals.