Menú
Reviews code changes for quality, security, and adherence to project standards. Use when reviewing PRs, commits, or staged changes.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Manually run a PHP code-cleanliness review on a file, at higher quality than the automatic background hook. Optional first argument is FULL or CHANGES; the last argument is the PHP file path.
Draft a standardized, reviewer-focused pull request description and - only after explicit approval - update the PR. Optional first argument is a PR number (defaults to the current branch's open PR). Optional argument is a Jira issue ID (e.g. ABC-123).
Research and understand a module, folder, or problem before implementing, capturing what you learn as local notes. Use before starting a complex task or to deepen understanding of an area. Optional argument is a module path/name and/or a Jira issue ID (e.g. ABC-123).
Run a PR readiness check on the current branch before opening or finalizing a pull request. Optional first argument is a Jira issue ID (e.g. ABC-123). Optional second argument is a base branch name.
| name | code-review |
| description | Reviews code changes for quality, security, and adherence to project standards. Use when reviewing PRs, commits, or staged changes. |
| argument-hint | [PR-number] |
When invoked, perform a thorough code review following these steps:
/code-review 123), fetch the PR diff using gh pr diff <number>git diff --cached, or if nothing staged, review uncommitted changes with git diffgit diff develop...<branch>Create a Markdown file report with the results and add it to ./temp/code-reviews including the PR id and title in the file name