collect-pr-info

Collect git commits and diffs to draft PR title and body JSON.

Updated Dec 6, 2025
One-click install
npx skills add https://github.com/reedom/claude-code-commands --skill collect-pr-info
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: collect-pr-info
Source: https://github.com/reedom/claude-code-commands/tree/main/gh/skills/collect-pr-info
Command: npx skills add https://github.com/reedom/claude-code-commands --skill collect-pr-info

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

PR creation often requires gathering diffs, commits, and context. This Skill automates data collection and returns a complete PR skeleton in JSON.

Core Features & Use Cases

  • Collects commit and diff data, drafts PR title and body, and handles a preceding PR update.
  • Outputs a ready-to-use JSON payload for PR creation agents.

Quick Start

Run the collect-info script to generate the PR data, then consume the JSON output.

Frequently Asked Questions about collect-pr-info

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

FAQPage Schema
How do I automate collecting PR data from git commits and diffs?

Collect PR data by running the collect-info script, which gathers commit messages, diffs, and repository metadata, then outputs a structured JSON payload ready for PR creation. This automates the manual work of assembling title, body, and branch information.

What information does the PR data JSON include?

The PR data JSON includes current_branch, target_branch, push_needed status, PR title and body, existing_pr reference, preceding_pr reference, and diff-split content. This gives you a complete skeleton for creating or updating pull requests.

Can I use this to generate PR content from a feature branch against main?

Yes. This Skill reads commits and diffs from your feature branch, compares against origin/main, and drafts PR title and body in the required format, handling branch validation and diff splitting automatically.

How does this Skill handle preceding PR updates?

The collected JSON includes preceding_pr data, allowing you to track and update related PRs in sequence. Error handling and cleanup logic ensure data consistency when managing dependent pull requests.

What do I need to do before running the collection script?

Prepare a feature branch with commits and ensure your repository is configured with origin/main as the target. The script reads git metadata directly, so no additional setup beyond standard git configuration is required.