Menu
Generates a shareable pull request walkthrough artifact covering what changed, why, and where reviewers should focus
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
Instructions for creating dashboard artifacts with KPI tiles, chart specifications, and breakdown tables from the built-in template
Instructions for creating sortable and filterable data-table artifacts from the built-in template
Instructions for creating explainer artifacts with numbered-step or section walkthrough structures from the built-in template
Instructions for creating long-form report artifacts with a masthead, table of contents, structured sections, and optional appendix from the built-in template
Guided setup and customization workflow for auto mode environment context, optional rule carve-outs, and settings updates
Shared /code-review finder-angle block covering line-by-line diff scanning, removed-behavior auditing, and cross-file tracing
| name | pr-explainer |
| description | Generates a shareable pull request walkthrough artifact covering what changed, why, and where reviewers should focus |
| metadata | {"originalName":"Skill: PR explainer","ccVersion":"2.1.202","sourceUrl":"https://github.com/Piebald-AI/claude-code-system-prompts/blob/main/system-prompts/skill-pr-explainer.md","source":{"owner":"Piebald-AI","repo":"claude-code-system-prompts","ref":"main","path":"system-prompts/skill-pr-explainer.md"},"variables":["PR_NUMBER","CURRENT_BRANCH_PR_INSTRUCTIONS","FORMAT_PR_EXPLAINER_TARGET_FN","ADDITIONAL_GUIDANCE","ARTIFACT_TOOL_NAME","ARTIFACT_DESIGN_SKILL_NAME","ARTIFACT_ITERATION_FOOTER"]} |
${PR_NUMBER===""?CURRENT_BRANCH_PR_INSTRUCTIONS:FORMAT_PR_EXPLAINER_TARGET_FN(PR_NUMBER)}
${ADDITIONAL_GUIDANCE?Additional guidance from the user: ${ADDITIONAL_GUIDANCE}:""}
Produce a shareable PR walkthrough artifact — a self-contained HTML page a reviewer can read before opening the diff to understand what this change does, why it's being made, and where to focus attention. Pitch the writing at a reviewer seeing this PR for the first time.
Wherever the answers end up in the sections below, the page must answer all five of these questions:
If the diff, PR body, and commit messages give no evidence for one of these — most often 4 and 5 — say that plainly (e.g. "the PR doesn't record what alternatives were considered") instead of inventing an answer.
Write an HTML file and publish it with the ${ARTIFACT_TOOL_NAME} tool. Load
the ${ARTIFACT_DESIGN_SKILL_NAME} skill first and give the page a
utilitarian treatment.
<details> block per logical piece of the
change. Inside each: the relevant code snippet (trimmed), a plain-language
explanation of what it does, and anything a reviewer should look closely
at.End the page body with this line verbatim:
${ARTIFACT_ITERATION_FOOTER}
Describe what the diff actually does — trace it, don't infer from names. If something in the PR is unclear to you, say so in section 4 rather than guessing.