KS
Killer-Skills

review-changes — Categories.community

v1.0.0
GitHub

About this Skill

Perfect for Code Review Agents needing automated Git repository analysis and UI validation capabilities. Design System that powers Razorpay

razorpay razorpay
[0]
[0]
Updated: 3/4/2026

Quality Score

Top 5%
55
Excellent
Based on code quality & docs
Installation
SYS Universal Install (Auto-Detect)
Cursor IDE Windsurf IDE VS Code IDE
> npx killer-skills add razorpay/blade/review-changes

Agent Capability Analysis

The review-changes MCP Server by razorpay is an open-source Categories.community integration for Claude and other AI agents, enabling seamless task automation and capability expansion.

Ideal Agent Persona

Perfect for Code Review Agents needing automated Git repository analysis and UI validation capabilities.

Core Value

Empowers agents to review Blade PRs by fetching diffs, checking CI status, and extracting Storybook preview URLs, utilizing Git and GitHub protocols for seamless integration.

Capabilities Granted for review-changes MCP Server

Automating PR reviews in the razorpay/blade repository
Validating UI changes with Storybook previews
Debugging CI status for failed builds

! Prerequisites & Limits

  • Requires GitHub access
  • Limited to razorpay/blade repository
  • Needs clarification on ShouldReviewUI and ShouldRunHeadedBrowser arguments
Project
SKILL.md
3.2 KB
.cursorrules
1.2 KB
package.json
240 B
Ready
UTF-8

# Tags

[No tags]
SKILL.md
Readonly

Review Blade PR

Review PRs in the razorpay/blade repository by fetching the diff, checking CI status, and extracting the Storybook preview URL.

Arguments / Clarifications (Use Cursor's AskQuestion tool to get clarifications)

  • PR: Link / Number of the PR to review
  • ShouldReviewUI: Whether UI should be reviewed or not. Get it clarified if not mentioned.
  • ShouldRunHeadedBrowser: Whether to run the browser in headed mode or not. Get it clarified if not mentioned.

Prerequisites

  • GitHub CLI (gh) must be installed and authenticated
  • agent-browser command must be installed (if ShouldReviewUI is true)

Guidelines

  • Avoid printing intermediate commentary; only output the final review in the main chat

Steps (Create checklist for each step)

1. Fetch the PR Diff and CI Status in Main Agent

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:

bash
1gh pr checks {PR_NUMBER} --repo razorpay/blade

If checks are failing / skipped, get the details from the checks on why they are failing / skipped

Use the following command (replace {JOB_ID} with the job id from the previous gh pr checks output):

bash
1gh run view --job {JOB_ID} --repo razorpay/blade

2. UI Review the Changes (if ShouldReviewUI is true)

  • Using agent-browser (Do NOT use Playwright MCP), open the Storybook URL (returned by earlier subagent)
    • agent-browser --help on docs on how to use it
  • Determine which URL to open based on the PR changes
  • agent-browser close to close any earlier opened browser instances
  • Open the URL with the agent-browser and test the functionality of the changes
    sh
    1agent-browser open {storybook_url} --headed (if ShouldRunHeadedBrowser is true)
  • Close the agent-browser at the end with agent-browser close

How to Find Changes

  • You can open the story outside iframe using the iframe.html url of storybook
    • E.g. 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
    • If iframe is not working, open the storybook url directly and find the story in the sidebar
  • If changes are in svelte components, check the svelte version of storybook on {storybook_base_url}/svelte/ route

Report the flows / features that were tested, if they are working as expected or not, and the issues found.

3. Code Review the Changes

Analyze the diff for:

  • Potential bugs or logic errors
  • TypeScript/type safety issues
  • Missing tests for new functionality
  • Accessibility concerns
  • Performance implications
  • API Breaking changes
  • Do not review the changes in the codebase, only review the changes in the diff.

Output Format

The subagent should return all the gathered information. Then in the main chat strictly following the output format mentioned in references/output-format.md

Related Skills

Looking for an alternative to review-changes or building a Categories.community AI Agent? Explore these related open-source MCP Servers.

View All

widget-generator

Logo of f
f

widget-generator is an open-source AI agent skill for creating widget plugins that are injected into prompt feeds on prompts.chat. It supports two rendering modes: standard prompt widgets using default PromptCard styling and custom render widgets built as full React components.

149.6k
0
Design

chat-sdk

Logo of lobehub
lobehub

chat-sdk is a unified TypeScript SDK for building chat bots across multiple platforms, providing a single interface for deploying bot logic.

73.0k
0
Communication

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
Communication

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
Communication