review-changes

Fetch diffs, verify CI status, and extract Storybook URLs for Blade PR reviews.

643|194|Updated Jan 28, 2020
One-click install
npx skills add https://github.com/razorpay/blade --skill review-changes-razorpay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-changes
Source: https://github.com/razorpay/blade/tree/main/.cursor/skills/review-changes
Command: npx skills add https://github.com/razorpay/blade --skill review-changes-razorpay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the Blade PR review workflow by fetching diffs, verifying CI checks, and extracting the Storybook preview URL, reducing manual effort and speeding up feedback loops.

Core Features & Use Cases

  • PR Diff Fetching: Retrieve the changes introduced in a PR to understand impact.
  • CI Status Verification: Check the latest CI status to determine if a PR is ready for review.
  • Storybook Preview Retrieval: Obtain the Storybook URL to share live previews with stakeholders.
  • Use Case: When reviewing razorpay/blade PRs, run this skill to quickly gather diff details, CI outcomes, and a ready-to-share preview link.

Quick Start

Use the skill to fetch the diff for PR #123 and retrieve its CI status and Storybook URL.

Frequently Asked Questions about review-changes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Blade PR reviews by fetching diffs and checking CI status?

Automating Blade PR reviews involves fetching pull request diffs, verifying the latest CI status to ensure builds pass, and extracting the Storybook URL to validate UI changes and share preview links with stakeholders.

Do I need GitHub CLI installed to fetch PR diffs and verify CI status?

GitHub CLI (gh) must be installed and authenticated to fetch PR diffs and verify CI status. Optionally, agent-browser is required for UI inspection when the ShouldReviewUI flag is set to true.

How does Storybook URL retrieval work during a pull request review?

Storybook URL retrieval extracts the live preview link generated by the PR's CI pipeline, allowing reviewers to visually inspect UI changes and share the interactive Storybook deployment directly with stakeholders.

Can I use this automated PR review workflow for repositories outside of Razorpay Blade?

This automated PR review workflow specifically targets Razorpay Blade pull requests within the main repository, relying on Blade-specific CI pipelines to fetch diffs, verify build statuses, and extract Storybook preview URLs.

What is the best way to share Storybook preview links with stakeholders after checking a PR diff?

The best way to share Storybook preview links is to run the automated review process, which retrieves the diff, confirms CI success, and outputs the ready-to-share Storybook URL for immediate stakeholder validation.