pr-review-postlisted

# pr-review-post Turn review findings into a posted PR review: one humanized note per file, tagging the author, under the user's account. Works on any repo/PR via `gh`. ## When to use The user wants findings **posted** to a GitHub PR as file-by-file inline comments (not one blob comment, not attributed to an AI). Pair it with any code-review pass for the analysis; this skill is the posting half. ## Voice (non-negotiable) - Collaborative teammate, not a linter. Praise what is good first. - Suggestions and questions ("Was that intentional?"), not commands. - Judgement calls stay soft ("not blocking", "at some point", "minor one"). - **No dashes** as separators or em-dashes in the comment text. Plain sentences. - One note per file (occasionally two if genuinely distinct). Each note begins with `@author` (the helper substitutes the real PR author login). - Never mention the assistant / AI. The user is the author of the review. ## Workflow 1. **Pin the PR.** Get `owner/name` and the PR number from the URL the user gives. 2. **Get findings.** Reuse a prior review pass if one exists; otherwise do a light two-axis pass (standards smells + spec). Only surface things worth the author's time. 3. **Draft per-file notes** in the voice above. Show them to the user and get explicit go-ahead before posting (posting is outward-facing). 4. **Post** with the helper (it auto-anchors to real diff lines, tags the author, clears any stale pending review, and folds un-anchorable no