Name: Refactor PR Summary
Author: Bryan-Roe-ai

Prompt file imported from Bryan-Roe-ai/Aria (.github/prompts/refactor-pr-summary.prompt.md). Copyright stays with the author.

Create a high-quality pull request summary for a refactor change set.

Optional companion:

Run /refactor-reviewer-checklist to generate a role-based review checklist for the same diff.
If unsure about sequencing, run /refactor-next-step.
Run /refactor-release-note to generate customer/internal release communication.
Run /refactor-handoff to package status and the exact next action for a teammate.
Run /refactor-merge-gate for an explicit GO/NO-GO decision before merging.
Run /refactor-rollback-plan to document concrete backout triggers and actions.
Run /refactor-workflow-audit if workflow-stage or command routing looks inconsistent.
Run /refactor-workflow-registry to normalize stage/command terms before handoff.
Run /refactor-routing-matrix to validate transition topology before handoff.

Inputs

Selected diff, changed files, and commit context
User arguments describing scope and rationale
Known unchanged contracts and invariants (API shapes, routes, streaming/status behavior)
Validation outcomes (focused and broader checks)

Required behavior

Keep the summary concise but complete for reviewers.
Separate what changed from what intentionally did not change.
Highlight risk areas and how they were mitigated.
Avoid fluff; prefer verifiable statements tied to evidence.

Non-goals unless explicitly requested

No modifying source code or test files.
No fabricating test results — summarize actual evidence only.
No including speculative improvements not yet implemented.

Output format

Title suggestion: one-line PR title
Why: problem or maintenance goal
What changed: grouped by file/area
Behavior parity / invariants preserved: explicit checklist
Validation: tests/checks run + outcomes
Risk & rollback notes: known caveats and backout path
Reviewer checklist: 3-7 concrete review points
Optional next command: one slash command

Optional add-ons when provided

Release note snippet
Changelog entry draft
Follow-up tasks (if deferred cleanup exists)

Optional next commands

/refactor-reviewer-checklist
/refactor-release-note
/refactor-merge-gate
/refactor-rollback-plan
/refactor-handoff
/refactor-done-check
/refactor-next-step
/refactor-command-cheatsheet
/refactor-workflow-audit
/refactor-workflow-registry
/refactor-routing-matrix

Example invocations

chat streaming refactor: summarize helper extraction, preserve SSE schema, include tests
provider cleanup PR: document fallback-order parity and readiness-check validation

Create a high-quality pull request summary for a refactor change set. Optional companion: - Run `/refactor-reviewer-checklist` to generate a role-based review checklist for the same diff. - If unsure about sequencing, run `/refactor-next-step`. - Run `/refactor-release-note` to generate customer/internal release communication. - Run `/refactor-handoff` to package status and the exact next action for a teammate. - Run `/refactor-merge-gate` for an explicit GO/NO-GO decision before merging. - Run `/refactor-rollback-plan` to document concrete backout triggers and actions. - Run `/refactor-workflow-audit` if workflow-stage or command routing looks inconsistent. - Run `/refactor-workflow-registry` to normalize stage/command terms before handoff. - Run `/refactor-routing-matrix` to validate transition topology before handoff. ### Inputs - Selected diff, changed files, and commit context - User arguments describing scope and rationale - Known unchanged contracts and invariants (API shapes, routes, streaming/status behavior) - Validation outcomes (focused and broader checks) ### Required behavior - Keep the summary concise but complete for reviewers. - Separate **what changed** from **what intentionally did not change**. - Highlight risk areas and how they were mitigated. - Avoid fluff; prefer verifiable statements tied to evidence. ### Non-goals unless explicitly requested - No modifying source code or test files. - No fabricating test results — summarize actual evidence only. - No including speculative improvements not yet implemented. ### Output format - **Title suggestion**: one-line PR title - **Why**: problem or maintenance goal - **What changed**: grouped by file/area - **Behavior parity / invariants preserved**: explicit checklist - **Validation**: tests/checks run + outcomes - **Risk & rollback notes**: known caveats and backout path - **Reviewer checklist**: 3-7 concrete review points - **Optional next command**: one slash command ### Optional add-ons when provided - Release note snippet - Changelog entry draft - Follow-up tasks (if deferred cleanup exists) ### Optional next commands - `/refactor-reviewer-checklist` - `/refactor-release-note` - `/refactor-merge-gate` - `/refactor-rollback-plan` - `/refactor-handoff` - `/refactor-done-check` - `/refactor-next-step` - `/refactor-command-cheatsheet` - `/refactor-workflow-audit` - `/refactor-workflow-registry` - `/refactor-routing-matrix` ### Example invocations - `chat streaming refactor: summarize helper extraction, preserve SSE schema, include tests` - `provider cleanup PR: document fallback-order parity and readiness-check validation`

{ "prompt": "Create a high-quality pull request summary for a refactor change set.\n\nOptional companion:\n\n- Run `/refactor-reviewer-checklist` to generate a role-based review checklist for the same diff.\n- If unsure about sequencing, run `/refactor-next-step`.\n- Run `/refactor-release-note` to generate customer/internal release communication.\n- Run `/refactor-handoff` to package status and the exact next action for a teammate.\n- Run `/refactor-merge-gate` for an explicit GO/NO-GO decision before merging.\n- Run `/refactor-rollback-plan` to document concrete backout triggers and actions.\n- Run `/refactor-workflow-audit` if workflow-stage or command routing looks inconsistent.\n- Run `/refactor-workflow-registry` to normalize stage/command terms before handoff.\n- Run `/refactor-routing-matrix` to validate transition topology before handoff.\n\n### Inputs\n\n- Selected diff, changed files, and commit context\n- User arguments describing scope and rationale\n- Known unchanged contracts and invariants (API shapes, routes, streaming/status behavior)\n- Validation outcomes (focused and broader checks)\n\n### Required behavior\n\n- Keep the summary concise but complete for reviewers.\n- Separate **what changed** from **what intentionally did not change**.\n- Highlight risk areas and how they were mitigated.\n- Avoid fluff; prefer verifiable statements tied to evidence.\n\n### Non-goals unless explicitly requested\n\n- No modifying source code or test files.\n- No fabricating test results — summarize actual evidence only.\n- No including speculative improvements not yet implemented.\n\n### Output format\n\n- **Title suggestion**: one-line PR title\n- **Why**: problem or maintenance goal\n- **What changed**: grouped by file/area\n- **Behavior parity / invariants preserved**: explicit checklist\n- **Validation**: tests/checks run + outcomes\n- **Risk & rollback notes**: known caveats and backout path\n- **Reviewer checklist**: 3-7 concrete review points\n- **Optional next command**: one slash command\n\n### Optional add-ons when provided\n\n- Release note snippet\n- Changelog entry draft\n- Follow-up tasks (if deferred cleanup exists)\n\n### Optional next commands\n\n- `/refactor-reviewer-checklist`\n- `/refactor-release-note`\n- `/refactor-merge-gate`\n- `/refactor-rollback-plan`\n- `/refactor-handoff`\n- `/refactor-done-check`\n- `/refactor-next-step`\n- `/refactor-command-cheatsheet`\n- `/refactor-workflow-audit`\n- `/refactor-workflow-registry`\n- `/refactor-routing-matrix`\n\n### Example invocations\n\n- `chat streaming refactor: summarize helper extraction, preserve SSE schema, include tests`\n- `provider cleanup PR: document fallback-order parity and readiness-check validation`", "variables": [], "notes": "Use when opening a refactor PR: generate a concise reviewer-friendly summary with parity evidence and test results. Arguments: Scope + rationale + key unchanged contracts + validation results (example: fn_app.py + SSE helper + /api/chat + passed).", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/Bryan-Roe-ai/Aria", "path": ".github/prompts/refactor-pr-summary.prompt.md", "ref": "2fc081c55a0d4bf937d08d8d5d6db567de265932", "url": "https://github.com/Bryan-Roe-ai/Aria/blob/2fc081c55a0d4bf937d08d8d5d6db567de265932/.github/prompts/refactor-pr-summary.prompt.md", "key": "Bryan-Roe-ai/Aria/.github/prompts/refactor-pr-summary.prompt.md" } } }

Refactor PR Summary

About

Inputs

Required behavior

Non-goals unless explicitly requested

Output format

Optional add-ons when provided

Optional next commands

Example invocations

Use it

Manifest

Reviews