القائمة
Cross-check a diff against the task packet's allowed/forbidden file lists; enforce R-001 scope boundaries with file:line evidence. Owned by the reviewer.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Keep commits atomic — split a mixed change set into scoped, reviewable commits.
The one-time procedure to take an exported project to live — understand it, confirm the name/goal/stack with the user, run the deterministic `aspis bootstrap`, enrich the judgment files (AGENTS.md, ARCHITECTURE, context), verify, and let the package self-clean. Followed by the bootstrap agent.
Keep per-subsystem architectural intent current through the planning loop — read before designing, record an impact report on change, confirm with the user, apply a dated update, and verify the build against approved intent.
Audit a plan's task dependency graph for structural integrity — circular dependencies, missing prerequisites, orphan tasks, and dependency classification (hard/soft/warning). Produces a pass/warn/fail audit report per dependency so planners catch graph errors before build starts.
Every editing agent should start on a clean working tree so parallel work never collides.
Verify hooks ran, no secrets, protected paths untouched, and commit message valid before committing. Owned by the reviewer.
| name | scope-compliance |
| description | Cross-check a diff against the task packet's allowed/forbidden file lists; enforce R-001 scope boundaries with file:line evidence. Owned by the reviewer. |
Before approving any change, verify every modified file is within the task packet's allowed scope and no forbidden files were touched. A single out-of-scope edit can corrupt the architecture or open a security hole. This is the deterministic half of the scope dimension: scripts check the file list, the reviewer interprets and judges. Reviewer is read-only (R-004) — it verifies, never edits.
Every change review, before any verdict. Also during plan review: does the plan's stated file list plausibly cover the scope it claims? Run alongside other reviewer skills (constitution-check, evidence-validation).
git diff --name-only HEAD~1 (or the appropriate
base — the last reviewed commit).TASK_PACKET.md /
TASKS.md / feature.yaml)..aspis/rules/**, profiles/defaults.yaml, .opencode/agents/**,
.claude/agents/**, secrets).file:line evidence.file:line list as evidence.A scope compliance report:
git diff --name-only).ALLOWED | FORBIDDEN | OUT-OF-SCOPE.CLEAN or CHANGES-REQUIRED.file:line evidence and a severity (CRITICAL / HIGH /
MEDIUM).git diff --name-only yourself.