Menu
Guidelines for reviewing Blade PRs — sanity checks, code quality, API decisions, usecase validity, and UI review.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Add React Native support (.native.tsx files) to Blade components that currently only have web implementations. Use when user says "add native support to {Component}", "migrate {Component} to native", or "/migrate-to-rn".
Resolve PR review comments by pushing code fixes or replying with explanations. Use when a PR has review comments that need to be auto-resolved.
Review blade PRs by fetching diff, checking CI status, and getting Storybook URL. Use when reviewing PRs, checking PR status, or getting preview links for razorpay/blade PRs.
Get agentic metrics for the `razorpay/blade` repo.
Perform a task end-to-end when intent is set to 'perform-task-end-to-end' by checking existence of GITHUB__RZP_SWE_AGENT_APP__APP_ID environment variable in the session.
Heal a Blade PR by fixing CI failures, missing changesets, and sanity issues. Use when a PR has failing CI or other sanity problems that need to be auto-fixed.
| name | code-review |
| description | Guidelines for reviewing Blade PRs — sanity checks, code quality, API decisions, usecase validity, and UI review. |
Use these guidelines to review a Blade PR. Apply each critique lens based on what the diff touches. No subagents — you perform the review directly.
Load and apply whichever references are relevant (they are referenced relative to this skill file path):
All issues raised by PR Sanity and API Decisions are critical and high importance issues. They take priority over any other code quality or other issues.
