Proposal: add Acceptable label for pragmatic PR review choices

[malhotra5]

Summary

Updates the github-pr-review skill to handle cases where the agent acknowledges that improvements can be made but are out of scope for the current PR, or when changes are pragmatic considering constraints.

Changes

• Added 🟢 Acceptable priority label - For acknowledging pragmatic trade-offs that are reasonable given constraints or out of scope for the PR
• Added "Pragmatic Choices" subsection - Explains when to use the Acceptable label:
  • When improvements are out of scope for the current PR
  • When the choice is pragmatic given project constraints (time, complexity, backwards compatibility)
  • When the trade-off is reasonable and doesn't introduce bugs or security issues
• Added example showing how to use the Acceptable label
• Updated Summary section to emphasize not blocking PRs for pragmatic choices

Example Usage

🟢 Acceptable: This helper could be extracted to a shared utility, but keeping it inline is reasonable for this PR's scope.

Rationale

This prevents the reviewer from marking items as "needs rework" when the code is a reasonable pragmatic choice, even if theoretically it could be improved in a future PR.

[enyst]

It's a bit unclear to me if this will work as I'm guessing we'd like it to work, but maybe. Let's try it.

(I'm guessing you'd like to nudge the LLM to not prevent itself from approving when it has some stuff to say that is arguably out of scope. An alternative there is to reply directly to that inline thread and tell it your decision and maybe even tell it to accept it - ha. It doesn't see top-level comments, but next review it will see the replies 😅)

[juanmichelini]

@enyst @malhotra5 I love this and need it, so I'm merging it.