reply-to-pr-thread

Topics in the source

• Reply to a GitHub PR review thread
• How to run
• Steps
• Why use this instead of gh api directly

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. Wraps the GitHub POST /repos/{owner}/{repo}/pulls/{pr}/comments/{id}/replies endpoint. Works for any review thread on any PR, but the canonical use case is replying to CodeRabbit threads — never resolve them, always reply with rationale. Body is always read from stdin. No --body / --body-file. Pipe text in or use a heredoc. On success, the command prints the new reply's htmlurl. Report that URL back to the user. 1. Identify the comment URL or comment ID. From the la-fetch-coderabbit-threads output, that's the URL printed in Comment 1 — coderabbitai. The integer after discussionr is the comment ID. 2. Compose the reply body. For a CodeRabbit-invalid case: lead with @coderabbitai, then 1–3 sentences explaining why the comment doesn't apply (cite the relevant CLAUDE.md rule, the existing test, or the commit hash where it was already addressed). 3. Pipe the body into the command. Capture the printed URL. 4. Never call any "resolve" mutation (resolveReviewThread GraphQL or its UI equivalent). This command (or la-reply-invalid-coderabbit, which adds the

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