review

Review pull requests for bugs, regressions, and convention violations with line-anchored findings.

11.6k|1.1k|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/emdash-cms/emdash --skill review-emdash-cms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/emdash-cms/emdash/tree/main/infra/flue-review/.flue/skills/review
Command: npx skills add https://github.com/emdash-cms/emdash --skill review-emdash-cms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reviews pull requests for real bugs, regressions, and convention violations, enumerating candidate issues across the diff, verifying each against the code, then returning structured line-anchored findings and a verdict. Read-only on GitHub; the orchestrator posts the review.

Core Features & Use Cases

  • Static, read-only PR review across diffs to identify real issues
  • Enumerates candidate problems, cross-checks with repository conventions (Lingui localization, RTL-safe Tailwind, SQL safety, API envelope shape, authorization, locale filtering on content tables, index discipline, changesets)
  • Returns a structured verdict with line anchors ready for posting as a review

Quick Start

Review a pull request on emdash-cms/emdash for real bugs, regressions, and convention violations, enumerate candidate issues across the diff, verify each against the code, and return a structured line-anchored findings report with a final verdict.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a pull request for code quality and convention violations?

Review a pull request by enumerating candidate issues across the diff and verifying each against repository conventions, returning structured line-anchored findings and a final verdict.

What is static analysis for PR review without running tests?

Static PR analysis reads the diff to identify real bugs and convention violations without executing tests or modifying the repository, ensuring a safe, read-only code review.

How do I check SQL safety and API envelope shape in a code diff?

Check SQL safety and API envelope shape by cross-referencing changes in the diff against established repository conventions, verifying each candidate issue before reporting findings.

Can I audit localization and RTL-safe Tailwind compliance in a pull request?

Yes, you can audit Lingui localization and RTL-safe Tailwind compliance by verifying the pull request diff against repository conventions and returning line-anchored findings.

Does the PR review process modify the repository or run tests?

No, the PR review process is strictly read-only and does not run tests or modify the repository, relying solely on static diff analysis to produce a verdict.