Review

Skill jmfontaine/jmf-claude-plugins/plugins/project-qa/skills/review

Claude Plugins

Install

npx -y skills add jmfontaine/jmf-claude-plugins --skill review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Review project files for consistency, completeness, and correctness. Use when asked to review, audit, check, or validate project configuration files (justfile, Makefile, CI workflows, pre-commit config, pyproject.toml, Dockerfile, docker-compose, etc.) or documentation files (README, CLAUDE.md, CONTRIBUTING, etc.). Supports both single-file review and cross-file consistency checks.

SKILL.md

2.5 KB, 477 tokens by cl100k_base, as published. Nobody here has run it

Project File Review

Review project files across three dimensions, then suggest fixes and improvements.

Dimensions

Consistency: Naming conventions, formatting, patterns, and style are uniform within and across files.
Completeness: Nothing is missing. All referenced targets, commands, variables, and dependencies exist. All expected sections are present.
Correctness: Syntax is valid. Commands work. Paths exist. Versions are compatible. Logic is sound.

Workflow

Phase 1: Individual File Review

Review each file separately. For each file:

Read the file fully.
Evaluate against all three dimensions.
Report findings grouped by dimension.
Suggest specific fixes with code snippets.

Phase 2: Cross-File Consistency

When multiple files are provided, or after individual reviews, check alignment across files:

Verify shared references match (e.g., target names in justfile match CI workflow steps, Python version in pyproject.toml matches CI matrix and Dockerfile).
Check that documented commands in README match actual targets/scripts.
Confirm dependency lists are synchronized (e.g., pyproject.toml vs requirements files vs CI install steps).
Ensure CLAUDE.md reflects the actual project structure and tooling.

Discovery Mode

When reviewing a file, suggest other project files that should be cross-checked. Common relationships:

justfile / Makefile <-> CI workflows, README, pre-commit config
pyproject.toml <-> Dockerfile, CI workflows, pre-commit config
README <-> CLAUDE.md, justfile, CI workflows
Dockerfile <-> docker-compose, CI workflows, pyproject.toml
pre-commit config <-> CI workflows, pyproject.toml

Offer to review related files the user hasn't mentioned yet.

Output Format

For each file, report:

### <filename>

#### Consistency
- [finding + suggested fix]

#### Completeness
- [finding + suggested fix]

#### Correctness
- [finding + suggested fix]

After all individual reviews, add a cross-file section:

### Cross-File Alignment
- [inconsistency + which files + suggested fix]

Omit empty sections. Prioritize actionable findings over nitpicks.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.