pr-review-inlinelisted

# /pr-review-inline Review a GitHub PR with `/pr-review-toolkit:review-pr`, then post each finding as an **inline line comment** (with a fix suggestion) on the exact problematic line. No summary comment — only line comments. Follow every step in order. Do not skip guards. Posting to a PR is outward-facing — never post without the per-issue selection gate in Step 8, and post only the findings the user selects there. **REQUIRED SUB-SKILL:** `use-worktree` (bundled in this repo) — Steps 3 and 5 use its `scripts/create-worktree.sh`. Installing pr-review-inline alone will fail at Step 3; install both. ## Personalize (fill before first use) The steps reference these placeholders — replace the example column with your values. | Placeholder | Meaning | Example | |---|---|---| | `<gh-wrapper>` | Prefix required for `gh` in your workspace (empty if none) | `direnv exec ~/workspace/acme` | | `<jira-site>` | Your Atlassian site (Step 2) | `acme.atlassian.net` | | `<ticket-regex>` | Ticket-key pattern extracted from the PR title/body | `ABC-\d+` | **Review voice** — Steps 7–8 write comment bodies and the closing ask in *your* review voice; replace this worked example with your own: - Bilingual Thai + English, terse — usually one short line. English for imperatives and technical terms; Thai for reasoning. Code identifiers stay English. - Direct but softened — Thai particles `ครับ`/`คับ`/`นะ`, or English `please`. - Prefer a question to push back when reconsideration is the point (`