add github PR review mechanics

[nickolasclarke]

Motivation and Context

How Has This Been Tested?

Breaking Changes

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[nickolasclarke]

sorry, poor form to open this as a draft. Claude got out ahead of its skis. I'll keep it here while I test this though to keep noise low.

[obra]

Ok, a first couple comments:

1. Thank you!
2. we no longer get to use when_to_use - official skills push that into description
3. this is a perfect example of the kind of stuff that goes in an ancillary document called maybe GITHUB-REVIEWS.md in the skill directory and gets mentioned but not @linked in the SKILL itself

[nickolasclarke]

Great. Yes this felt perhaps the wrong place to put this, and wanted this very discussion! Happy to move into its own markdown.