القائمة
Generates a context-specific audit brief and executes review via code-reviewer agent. Usable standalone or as a building block within other skills.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Full SDLC workflow - from task to PR. Plans, audits adversarially, implements, runs quality gates, and opens a PR.
Generates a PR description from the current branch diff and project conventions. Output is a ready-to-use markdown body.
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Validates project.yaml is well-formed. Checks required fields, valid values, resolvable paths, and detects typos.
Validates code against all project architecture conventions. Reads project.yaml to determine applicable checks and runs them. Replaces individual check-* skills.
| name | audit |
| description | Generates a context-specific audit brief and executes review via code-reviewer agent. Usable standalone or as a building block within other skills. |
| skills | check-conventions |
| agents | code-reviewer |
Analyzes changes, generates a brief adapted to the specific work, and spawns code-reviewer to execute the review.
/audit or invoked programmatically by other skills (e.g. implement).
Accepts one of:
git diff --stat
git diff --cached --stat
Or use the provided branch/file list. Read changed files.
Craft a self-contained audit brief specific to this change. The brief adapts to what was done:
For new feature code:
For bug fixes:
For refactors:
Always include in the brief:
project.yaml)rule://writing-style (verbatim) with instruction: report findings using this styleSpawn code-reviewer agent with the generated brief. Return its output verbatim.
The code-reviewer verdict: structured findings (Critical/Important/Nit) + PASS/FAIL.
When called with prior findings to verify (e.g. implement's final audit):
Brief focuses on: