Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

Começar

code-review

Estrelas640

Forks194

Atualizado11 de junho de 2026 às 07:16

Guidelines for reviewing Blade PRs — sanity checks, code quality, API decisions, usecase validity, and UI review.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

razorpay

razorpay/blade

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de garantia de qualidade de software e testadoresInformática e Matemática·SOC 15-1253

Explorador de arquivos

7 arquivos

SKILL.md

readonly

name	code-review
description	Guidelines for reviewing Blade PRs — sanity checks, code quality, API decisions, usecase validity, and UI review.

Blade PR Code Review Guidelines

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.

Arguments

Identify PR_NUMBER from the PR link.

Critique Lenses

Load and apply whichever references are relevant (they are referenced relative to this skill file path):

PR Sanity — Always relevant. CI status, changeset coverage, docs, tests → pr-sanity-critique.md
API Decisions — Relevant for component changes. prop naming, component structure, design system consistency (apply when diff touches component files) → api-decision-critique.md

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.

Mais deste repositório

mesmo repositório

migrate-to-rn

razorpay/blade

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".

2026-07-14640

resolve-comments

razorpay/blade

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.

2026-07-10640

review-pr

razorpay/blade

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.

2026-07-09640

get-agentic-blade-metrics

razorpay/blade

Get agentic metrics for the `razorpay/blade` repo.

2026-06-24640

perform-task-end-to-end

razorpay/blade

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.

2026-06-24640

heal-pr

razorpay/blade

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.

2026-06-23640

name	code-review
description	Guidelines for reviewing Blade PRs — sanity checks, code quality, API decisions, usecase validity, and UI review.

Blade PR Code Review Guidelines

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.

Arguments

Identify PR_NUMBER from the PR link.

Critique Lenses

Load and apply whichever references are relevant (they are referenced relative to this skill file path):

PR Sanity — Always relevant. CI status, changeset coverage, docs, tests → pr-sanity-critique.md
API Decisions — Relevant for component changes. prop naming, component structure, design system consistency (apply when diff touches component files) → api-decision-critique.md

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.