pr-preparelisted

# pr-prepare Most PRs that contain AI-authored code skip the disclosure that reviewers need to evaluate them properly. This skill produces PR descriptions that make AI authorship, change classification, and verification status explicit — so reviewers know which sections need line-by-line attention and which can be spot-checked. It also draws the change as a diagram, because reviewers grasp structure far faster from a picture than from a file list. ## When to use Use whenever the user is about to open or push a PR. Triggers include: - "Prepare a PR / open PR / push for review" - "Write a PR description" - "I'm done with the feature, ready to ship" - "What should I put in the PR description" - Any time the user mentions merging, pushing, or pulling-request a branch Skip only if the user explicitly says "I'll write the PR myself" or wants raw diff output. ## Workflow ### Step 1 — Read the change Use Bash to gather: - `git status` — what's staged / dirty - `git log <base>..HEAD --oneline` — commit messages on the branch - `git diff <base>...HEAD --stat` — file-level summary - `git diff <base>...HEAD` for any small files; for large diffs, sample changed sections While reading, note the _shape_ of the change as well as its content — which files/packages/services are new, which are modified, and how they call each other. This is the raw material for the diagram in Step 6. If `<base>` isn't obvious, ask the user (commonly `main` or `develop`). ### Step 2 — Ask about AI au