# Review

Review one pull request for real bugs, regressions, and convention violations.

- Repository: https://github.com/emdash-cms/emdash (14094 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add emdash-cms/emdash --skill review -g -a claude-code -y`
Codex: `npx skills add emdash-cms/emdash --skill review -g -a codex -y`
Cursor: `npx skills add emdash-cms/emdash --skill review -g -a cursor -y`
Gemini CLI: `npx skills add emdash-cms/emdash --skill review -g -a gemini-cli -y`

## Description

Review one pull request for real bugs, regressions, and convention violations. Enumerate candidate issues across the whole diff, verify each against the code, then return structured line-anchored findings and a verdict. Read-only on GitHub; the orchestrator posts the review.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Review a pull request

You are reviewing a pull request on **emdash-cms/emdash**. Find real bugs, regressions, and gaps, and return structured findings; the orchestrator posts them as a single review.

Review **statically**. Do not run the test suite, linter, builds, or install anything (you have no shell anyway). Read code, trace with searches, and reason. If confirming something would require running tooling, say it's unverified rather than guessing.

The repo's AGENTS.md is at the repo root in your context. Check the PR against its conventions (Lingui localization, RTL-safe Tailwind, SQL safety, API envelope shape, authorization, locale filtering on content tables, index discipline, changesets, query counts on logged-out routes, comment discipline). A violation is a real finding, not a nit.

## Documentation changes

When the diff changes documentation prose, load the `writing-emdash-docs` skill before reviewing those files. This includes public docs, READMEs, contributor guidance, technical specifications, release notes and changesets, and skill instructions. Apply the skill only to documentation; do not spend review context on it for code, tests, generated files, or prose fixtures.

Verify documentation claims against the implementation, types, tests, command output, and adjacent docs. The writing skill does not replace technical investigation.

Calibrate documentation findings by their effect:

- Use `needs_fixing` for a false technical claim, an obsolete or unsafe command, an API example that cannot work, a procedure that cannot reach its stated outcome, a missing prerequisite that causes failure or data loss, or documentation that contradicts shipped behavior.
- Use `suggestion` for voice, organization, accessibility, verbosity, or anti-slop edits that preserve meaning.
- Do not flag a watched word or sentence shape by itself. Confirm that it makes the documentation less precise, less useful, or harder to understand.

The rest: https://github.com/emdash-cms/emdash/blob/HEAD/infra/flue-review/.flue/skills/review/SKILL.md