summarize_pull-requests — Claude Code prompt: setup and usage
Turns a repository pull request log into a one-sentence summary followed by key PRs rewritten in clear language.
.claude/commands/summarize_pull-requests.mdWhat summarize_pull-requests does
This prompt converts pull request lists into structured Markdown. It creates two output sections: SUMMARY: containing a single sentence on overall repository activity, and TOP PULL REQUESTS: listing major submissions.
Instructions require converting shorthand or messy PR titles into clear descriptions. All conversational filler, notes, and warnings are barred from the response.
To generate anything meaningful, feed it real PR logs from Git or GitHub CLI. Without input records, the prompt produces no useful data.
What it helps with
- draft a pull request digest for a release note
- rewrite cryptic PR titles into plain language
- summarize recent repository activity from Git history
Example prompts for the agent
- Summarize the latest open pull requests using the
summarize_pull-requestsprompt - Run
summarize_pull-requestson this list of recent PRs from GitHub
How to install summarize_pull-requests
Manually: put the files in place
.claude/commands/summarize_pull-requests.mdHow to use
Paste the text at the start of a chat or into project instructions
Command from the source
fabric --pattern summarize_pull-requestsQuestions about summarize_pull-requests
How do I install summarize_pull-requests in Claude Code?
Save the prompt file to .claude/commands/summarize_pull-requests.md. In the fabric CLI tool, run fabric --pattern summarize_pull-requests instead.
What does summarize_pull-requests do?
It reads pull request entries and outputs Markdown with a one-sentence summary alongside key PRs rewritten for clarity.
Does summarize_pull-requests include explanations or notes?
No, the prompt explicitly suppresses conversational filler, warnings, and notes, outputting only the requested Markdown sections.
Source text
summarize_pull-requests · MIT
# IDENTITY and PURPOSE You are an expert at summarizing pull requests to a given coding project. # STEPS 1. Create a section called SUMMARY: and place a one-sentence summary of the types of pull requests that have been made to the repository. 2. Create a section called TOP PULL REQUESTS: and create a bulleted list of the main PRs for the repo. OUTPUT EXAMPLE: SUMMARY: Most PRs on this repo have to do with troubleshooting the app's dependencies, cleaning up documentation, and adding features to the client. TOP PULL REQUESTS: - Use Poetry to simplify the project's dependency management. - Add a section that explains how to use the app's secondary API. - A request to add AI Agent endpoints that use CrewAI. - Etc. END EXAMPLE # OUTPUT INSTRUCTIONS - Rewrite the top pull request items to be a more human readable version of what was submitted, e.g., "delete api key" becomes "Removes an API key from the repo." - You only output human readable Markdown. - Do not output warnings or notes—just the requested sections. # INPUT: INPUT: <!-- user.md -->
© danielmiessler · MIT · danielmiessler/Fabric
