More screenshots
Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+21 moreClaude CodeCursorCodex CLIMuseDots
Manus
Grok
Grok Bot+18 agentsPR Review Preparer
A 1,400-line PR with the description 'fixes stuff' doesn't get reviewed — it gets skimmed, approved, and becomes next quarter's bug.
$8.99
PR Review Preparer
Example session with this skill installed
Prepare my PR for review. It adds retry handling for Stripe webhooks in our Django app: 14 files, about 620 changed lines, including a new migration, a refactor of payments/services.py, and some formatting changes in unrelated files. Should I split it?
- Read your context and instructions
- Compiled the pr review preparer
Review package for the Stripe webhook retry PR, with a recommendation to split it in two.
Self-review sweep
- Revert or move the formatting-only changes in unrelated files
- Confirm the migration is reversible and has no data changes mixed in
- Check retries are idempotent: the same event ID must not be processed twice
- Remove debug logging and commented-out code in payments/services.py
Split recommendation
Yes. Open
PR 1: refactor payments/services.py (no behaviour change) first, then
PR 2: webhook retries + migration on top. Reviewers can then check the refactor for equivalence and the retry logic for correctness separately.
Description (PR 2)
Why: Failed Stripe webhooks are currently dropped. This adds retries so events are not lost.
What: Stores event IDs, retries failed handlers, skips already-processed events.
Not in scope: Changes to payment flows or Stripe API calls.
Risks
| Risk | Mitigation |
|---|---|
| Duplicate processing | Unique constraint on event ID |
| Migration on a live table | Additive only, test the rollback before merging |
Reading order
- Migration
- Event model
- Webhook view
- Tests
Next steps
- Split the branch and open the refactor PR first
- Add a test that replays the same event twice
- Paste the description above into PR 2
Connects securely to your tools. The creator never sees your data.
About this skill
A 1,400-line PR with the description 'fixes stuff' doesn't get reviewed — it gets skimmed, approved, and becomes next quarter's bug. This skill writes the PR description your reviewers actually need: the why behind each change, the risk surface to focus on, the areas that deserve careful reading vs. the mechanical changes that don't, and the testing evidence that reduces the reviewer's work. It also structures your changes so reviewers can understand the intent before reading any diff. Use it before you open the PR — give it your diff summary, the issue you're solving, and any context your reviewers don't have; it returns a description that gets your PR read seriously instead of rubber-stamped.
- Cannot resolve merge conflicts. - Does not actualy push code to the repository. - May need manual clarification for very large refactors.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 months ago
Permissions
No special permissions declared or detected