pr-explainerlisted

--- name: pr-explainer description: Generate a shareable walkthrough artifact for a pull request — what changed, why, and a reviewer-oriented before/after narrative. --- No PR number was given — explain the current branch's pending PR: 1. `git log --oneline @{upstream}..HEAD` for the commit list (fall back to `origin/main..HEAD` if no upstream) 2. `git diff @{upstream}...HEAD` for the unified diff ## Goal 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: 1. What is the problem this PR is trying to solve? 2. Why is it a problem? 3. How are we solving it? 4. What alternatives did we consider? 5. Why is the current approach better than the alternatives? 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. ## Build it from the explainer template Load the `artifact-explainer` skill and build the page from its template, publishing with the Artifact tool as that skill directs. Use the template's **sections flavor** — keep the sections structure, delete the numbered steps. F