Menu
Generates a summary of a pull request based on the PR description and the code changes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Diagnose and fix a spend plan PDF that isn't parsing correctly. Takes a filename or URL and optional free-form agency/bureau hint, then diagnoses what's failing, explains the proposed fix, and applies it across load-file.ts, spend-plan-agency-match.ts, and the test file.
Use when doing infrastructure work.
Manages project dependencies, ensuring all required packages are installed and up to date.
Use when updating or checking GitHub Action versions, when adding a new action to a workflow file, or when the Developer asks about action versions or SHA pins.
Audits and fixes the `.claude/` directory to ensure internal consistency, correct references, and adherence to project conventions.
On-demand security review of code changes. Use when asked to "security check", "security review", "find vulnerabilities", "check for security issues", "audit security", or "OWASP review". Diff-aware, covers OWASP Top 10, supply chain, infrastructure, and agentic AI security with confidence-based reporting.
| name | pd-summarize-pr |
| description | Generates a summary of a pull request based on the PR description and the code changes. |
When the Developer indicates that work is ready for a pull request, output a filled-out version of the PR template located at .github/pull_request_template.md. Follow the guidelines in rules/PULL_REQUESTS.md for how to fill out the template, including linking to relevant issues, summarizing the change, noting side effects, flagging open questions, providing testing instructions, and checking off completed items.
To get the set of actual changes, use the following:
git diff main... to get the diff of all changes since branching off main.This is important:
.github/pull_request_template.md template.Output to the Developer for a review, but also write the output to a .pr_summary_<branch-name>.md file in the project root for easier copy and paste.
Things to look out for:
git diff to see if there are uncommitted changes. If there are, ask the Developer to commit them before making the PR output.