con un clic
review-changes
// 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.
// 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.
Orchestrate parallel migration of Blade React components to Svelte 5. Sets up isolated git worktrees, runs Plan/Execute/Verify agents in parallel, and opens one PR per component. Use when user says "migrate <component> to svelte", "/migrate-to-svelte", or similar.
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.
Visually verify component changes in Storybook using the agent-browser CLI tool
Get agentic metrics for the `razorpay/blade` repo.
Important guidelines for writing frontend UI code. Ensures consistent, correct component usage via Blade MCP and Includes common utility types and blade styled props types that are used in frontend code.
Create a draft pull request with conventional commit message and structured PR body targeting master branch
| name | review-changes |
| description | 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. |
| disable-model-invocation | true |
Review PRs in the razorpay/blade repository by fetching the diff, checking CI status, and extracting the Storybook preview URL.
gh) must be installed and authenticatedagent-browser command must be installed (if ShouldReviewUI is true)https://patch-diff.githubusercontent.com/raw/razorpay/blade/pull/{PR_NUMBER}.diff
(Ignore the lock file changes from diff)
Fetch status checks once and extract both CI status and Storybook URL:
gh pr checks {PR_NUMBER} --repo razorpay/blade
Use the following command (replace {JOB_ID} with the job id from the previous gh pr checks output):
gh run view --job {JOB_ID} --repo razorpay/blade
agent-browser --help on docs on how to use itagent-browser close to close any earlier opened browser instancesagent-browser open {storybook_url} --headed (if ShouldRunHeadedBrowser is true)
agent-browser closeiframe.html url of storybook
https://61c19ee8d3d282003ac1d81c-rzqbxanzgn.chromatic.com/?path=/story/components-datepicker--date-picker-presets-with-display-format-compact this story can be opened as an iframe in https://61c19ee8d3d282003ac1d81c-rzqbxanzgn.chromatic.com/iframe.html?args=&id=components-datepicker--date-picker-presets-with-display-format-compact&viewMode=story{storybook_base_url}/svelte/ routeReport the flows / features that were tested, if they are working as expected or not, and the issues found.
Analyze the diff for:
The subagent should return all the gathered information. Then in the main chat strictly following the output format mentioned in references/output-format.md