fetch-coderabbit-threads

Topics in the source

• Fetch unresolved CodeRabbit review threads from a PR
• How to run
• Output
• Steps
• Why this skill

Preflight: run la-doctor --plugin once per session before using any la- or dr- command; if it fails, stop and show the user its output. Works in any repo; it does not read living-architecture.yaml. — required, the PR number. --repo OWNER/REPO — optional; defaults to the repo of the current git directory (auto-detected via gh repo view). --all-authors — include unresolved threads from any author, not just CodeRabbit. Always emits both formats side-by-side: Markdown to stdout — one section per inline thread (URL, file:line, author, resolved/outdated, each comment body), followed by ## CodeRabbit review-summary nitpicks and ## CodeRabbit outside-diff-range comments sections. JSON file — full filtered payload at ${TMPDIR:-/tmp}/coderabbit-threads- - .json. The path is printed on the last line, prefixed JSON: . The JSON schema is: 1. Run the script with the PR number the user gave (or, if they didn't say, infer from gh pr view --json number -q .number). 2. Read the Markdown output and present a concise summary to the user — count, files touched, visible severity. Re-parse the JSON file (no extra API call) if you need structured data. 3. Never call any "resolve" mutation or click "Resolv

This is an excerpt. Refer to the complete source and its current requirements.