review_skill

This skill reviews PRs using comprehensive criteria across security, correctness, performance, accessibility, i18n, and code quality to speed up reviews.
  • TypeScript

1.7k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill quran/quran.com-frontend-next --skill review

  • SKILL.md4.4 KB

Overview

This skill reviews pull requests using a comprehensive checklist focused on security, correctness, clean code, TypeScript, React patterns, i18n/RTL, performance, and accessibility. It is tailored for a Next.js frontend in TypeScript and produces structured, actionable review reports ready for posting to GitHub.

How this skill works

For each PR the skill fetches metadata and the diff, consults a detailed review prompt, and applies a layered checklist across critical, standard, clean code, polish, testing, and regression categories. It detects large changes that may need splitting, checks for previous reviews and re-review status, and outputs a formatted review with categorized issues, positives, and a verdict.

When to use it

  • Reviewing a single pull request before merge
  • Auditing multiple related PRs in a chain
  • Performing a re-review after author updates
  • Validating changes that touch security, i18n, or accessibility
  • Checking PRs that modify shared UI, state, or build config

Best practices

  • Run automated checks locally (yarn test, yarn lint, yarn build) before deep review
  • Flag PRs with >15 changed files for potential splitting
  • Always check previous review comments and commits since last review
  • Prioritize security, regressions, and user-facing breakages first
  • Provide concise, categorized findings and clear remediation steps

Example use cases

  • A feature PR adding new pages and API calls in Next.js
  • A refactor that touches shared components and state management
  • A localization change that may affect RTL layout and hardcoded strings
  • A performance patch that changes memoization or bundle boundaries
  • A re-review after an author claims previous issues were fixed

FAQ

It fetches prior reviews and comments, summarizes status, lists key issues raised, checks commits since last review, and focuses on whether feedback was addressed and if regressions were introduced.

What are the top priorities in a review?

Address critical issues first: security, correctness, breaking changes, and error handling. Then evaluate TypeScript, React patterns, i18n/RTL, performance, accessibility, and clean code.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational