review

Generate diff-scoped inline review comments for GitHub pull requests and GitLab merge requests.

Updated May 20, 2026

Search Tags:#typescript #accessibility #github #pr review #gitlab #inline comments #css architecture

One-click install

npx skills add https://github.com/semanticpixel/abc --skill review-semanticpixel

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/semanticpixel/abc/tree/main/plugins/abc/skills/review
Command: npx skills add https://github.com/semanticpixel/abc --skill review-semanticpixel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces the time and cognitive load of reviewing pull requests and merge requests by generating precise, actionable feedback focused on semantic HTML, CSS architecture, accessibility, TypeScript patterns, and code quality.

Core Features & Use Cases

Auto platform detection: Reviews GitHub PRs or GitLab MRs based on a URL, a PR/MR number, or the current git remote.
Diff-scoped, positional comments: Analyzes only changed/new lines and posts inline suggestions with line-accurate placement.
Approval-gated posting: Presents a numbered set of proposed comments for user approval and posts only what the user allows.
Repo-specific rule support: Optionally reads .claude/review-rules.md to apply project-specific review opinions when present.
Review depth scaling: Adjusts thoroughness based on PR/MR size, skipping style nits for large changes and prioritizing errors, security, and accessibility.

Quick Start

Run the review by saying: review a PR or MR URL (or its number) so you can approve the proposed inline comments before they get posted.

Frequently Asked Questions about review

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

FAQPage Schema

How do I automate inline PR review comments for TypeScript and accessibility issues?▼

Automating inline PR review generates diff-scoped, line-accurate suggestions for TypeScript patterns, semantic HTML, and accessibility, limiting output to changed lines. You approve proposed comments before they get posted directly to GitHub or GitLab.

Can I review a GitLab merge request using a URL or MR number?▼

Yes, reviewing a GitLab merge request works by auto-detecting the platform from a URL, MR number, or current git remote. The review analyzes only changed lines and proposes inline comments for your approval before posting.

How do I customize automated code quality reviews with project-specific CSS architecture rules?▼

To customize code quality reviews with project-specific CSS architecture rules, place a review-rules.md file inside the .claude directory. The review process loads this repository context and applies your custom review opinions to the inline feedback.

Does PR review feedback adjust based on the size of the pull request?▼

PR review feedback scales its depth based on pull request size. For large changes, it skips style nits and prioritizes errors, security, and accessibility issues, ensuring reviews remain focused and actionable on substantial diffs.

What is the best way to prevent duplicate inline comments on an existing GitHub pull request discussion?▼

The best way to prevent duplicate inline comments is deduping proposed feedback against existing GitHub pull request discussions. The review mechanism checks current threads and limits new suggestions to changed lines before requesting your approval.

Why are my inline CSS architecture suggestions limited to changed lines in the diff?▼

Inline CSS architecture suggestions are limited to changed lines to reduce cognitive load and ensure precise, actionable feedback. This diff-scoped positional anchoring targets only new or modified code, skipping untouched lines entirely.