Add PR Bridge extension to community catalog

[Quratulain-bilal]

Summary - Adds PR Bridge extension to the community catalog and README - 3 commands: /speckit.pr.generate, /speckit.pr.checklist, /speckit.pr.summary - 1 hook: after_implement — auto-generate PR description after implementation - Original contribution — closes the missing final step in the SDD workflow ## The Problem Spec Kit's workflow ends at /speckit.implement. After building a feature, developers manually write

PR descriptions from scratch — even though all the information already exists in spec.md, plan.md, and
tasks.md. This extension bridges that gap.

The SDD Loop (Now Complete)

/speckit.specify → spec.md What to build
/speckit.plan → plan.md How to build it
/speckit.tasks → tasks.md Step-by-step tasks
/speckit.implement → code Build it
/speckit.pr.generate → PR description ← NEW: Tell reviewers what you built

Commands

Command	Purpose
/speckit.pr.generate	Complete PR body: title, summary, requirement checklist, task progress, test
plan
/speckit.pr.checklist	Reviewer checklist mapping each spec requirement to implementing files and
tests
/speckit.pr.summary	Concise spec-intent-vs-implementation comparison for stakeholders

All commands are read-only — they generate text, never create or push PRs directly.

Key Features

• Maps every spec requirement to its implementing files with ⚠️ gap detection
• Adapts to .github/PULL_REQUEST_TEMPLATE.md if one exists
• Graceful degradation — works with just spec.md if plan.md/tasks.md are missing
• Conventional commit title format (feat:, fix:, refactor:)

Changes

• extensions/catalog.community.json — added pr-bridge entry (alphabetical, between
  plan-review-gate and presetify)
• README.md — added extension row (alphabetical, between Plan Review Gate and Presetify)
• Bumped top-level updated_at to 2026-04-10

Extension repo

https://github.com/Quratulain-bilal/spec-kit-pr-bridge-

[Quratulain-bilal]

@mnriem

This is an original contribution — not from an issue request, but from a gap I noticed in the SDD
workflow.

Spec Kit covers specify → plan → tasks → implement beautifully. But then the developer has to manually
write a PR description from scratch — even though all the information already exists in spec artifacts.

PR Bridge closes that loop. It reads spec.md, plan.md, tasks.md, and git diff to auto-generate:

• Complete PR descriptions with requirement traceability
• Reviewer checklists mapped to spec requirements and implementing files
• Change summaries comparing spec intent with actual implementation

Every section traces back to a spec artifact. Requirements without matching code get flagged with ⚠️.
All three commands are read-only.

This makes the SDD workflow end-to-end: from specification all the way to pull request.