Menu
Use this skill when the user asks to run checks, validate a change, see whether code is ready, or investigate lint, analysis, test, or security-gate results in a Symfony/API Platform project.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use this skill when the user reports broken behavior, errors, regressions, failing tests, or asks to fix a bug. Trigger on requests like "this is broken", "fix this bug", "the test fails", or "there is a regression".
Use this skill when the user asks to improve agent instructions, update Claude guidance, review drift in CLAUDE.md or .claude files, or keep the repo guidance aligned with how the project actually evolves.
Use for bug fixes, refactors, reviews, or ambiguity-heavy implementation tasks to reinforce explicit assumptions, minimal diffs, simplicity, and direct verification.
Use this skill when the user asks to add, create, implement, or build new functionality in a Symfony/API Platform project. Trigger on requests like "add an endpoint", "implement a feature", "create a command", or "build this behavior".
Use this skill when the user asks to prepare a commit, write a commit message, stage files, create a branch, prepare PR notes, or mentions Conventional Commits. Trigger on requests like "prepare the commit", "write the commit message", "stage this and prepare a PR", or "help me commit these changes".
Use this skill when the user asks for a code review, a correctness pass, a check before PR, or asks whether a Symfony/API Platform change follows project conventions. Trigger on "review this", "check my changes", or "is this implementation correct?".
| name | verify-quality |
| description | Use this skill when the user asks to run checks, validate a change, see whether code is ready, or investigate lint, analysis, test, or security-gate results in a Symfony/API Platform project. |
Use this skill to run the repository's real quality gates in a predictable order.
Read first:
.claude/rules/testing.mdRead as needed:
Makefilecomposer.jsonWorkflow:
make targets over raw vendor binaries.Typical order:
make quality (runs lint, analyse, rector together)make tests-unitmake tests-integrationmake testsmake tests-apimake securityFor targeted runs only (skip if running make quality):
make lintmake analysemake rectorRules: