Menu
Review repository code changes in the current local branch or an explicit diff. Use for prompts like "review", "review this branch", "code review", "pre-PR review", "review current branch", and "review my changes".
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Folio and host-app testing conventions. Use when adding, changing, debugging, or reviewing tests, test helpers, factories/fixtures, mocks, stubs, ViewComponent tests, JavaScript behavior tests, integration/system coverage, or files under test/ and packs/*/test.
Folio “HTML over wire” JSON APIs: controllers use render_component_json so the response body is JSON with a string "data" key holding rendered ViewComponent HTML; JavaScript uses Folio.Api.apiGet/apiPost and response.data, not pure domain JSON for client-side rendering. Use when adding or changing render_component_json, console/API endpoints that return component fragments, or consumers of response.data as HTML.
JavaScript conventions for Folio: ES6+, StandardJS linting, DOM APIs, Folio.Api fetch wrappers, debounce/throttle, flash events, and when to use Stimulus. Use when writing or editing .js files, adding behavior to components, or when the user asks about JavaScript patterns in Folio.
Folio optional pack boundary and namespace rules. Use when editing files in optional pack directories, adding pack controllers/components/models/lib code, wiring routes to pack code, or moving reusable behavior between a host app, the Folio engine, and an optional pack, including Packwerk verification.
Build or change Folio SimpleForm inputs and extensions: app/inputs classes, SimpleForm::Inputs overrides, register_stimulus wiring, input_controls, custom_html, standalone input JS/Sass assets, and rendered HTML tests.
Slim template formatting and best practices for Folio components and views. Use when writing or editing .slim templates, reviewing Slim formatting, or when the user asks about Slim conventions, multi-line attributes, or template structure in Folio.
| name | code-review |
| description | Review repository code changes in the current local branch or an explicit diff. Use for prompts like "review", "review this branch", "code review", "pre-PR review", "review current branch", and "review my changes". |
Review Folio repository changes and produce review feedback only. Do not modify files or propose a patch branch unless the user explicitly asks for fixes.
AGENTS.md before reviewing.AGENTS.md to decide which .skills/*/SKILL.md
files apply to the changed files.origin/master.git diff --name-only <base>...HEAD.git diff <base>...HEAD.AGENTS.md or skill rules.AGENTS.md, an
applicable skill, or would cause maintenance problems.Start with findings, ordered by severity. Use this final review structure:
### Findings
**1. [WARNING] Concise issue title**
```text
path/to/file.rb:123
```
Explain the bug or risk, why it matters, and the expected fix.
If there are no findings:
No findings.
### Overall Assessment
Briefly summarize review confidence and residual risk.
### Context Used
List the `AGENTS.md` files, `.skills/*/SKILL.md` files, and diff base used.
For each finding, include [CRITICAL], [WARNING], or [SUGGESTION], a
concise title, an exact file and line reference, and the expected fix. If there
are no findings, mention any remaining test gaps or residual risk in the
overall assessment.
Keep summaries brief. Do not include raw command transcripts, token counts, review checklists, or long code snippets.