القائمة
Apply the reviewer-owned architecture-constitution checks (from the system-of-record YAML) before issuing a review verdict.
التثبيت باستخدام 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 | constitution-check |
| description | Apply the reviewer-owned architecture-constitution checks (from the system-of-record YAML) before issuing a review verdict. |
During review, verify that the built change honours the architecture constitution
— specifically the checks the reviewer owns per the constitution's
constitution-checks.yaml. This is the review-time counterpart to the planning-
lead's constitution-checks (which audits the PLAN); this skill audits the
built artifact against the constitution.
The system of record for the rules is
src/aspis/data/catalog/config/policy/constitution-checks.yaml — load the
rule list from it, never re-derive it from the prose constitution document.
R-006 single-source: one fact, one owner; this skill walks the YAML, not its
own hard-coded list.
src/aspis/data/catalog/config/policy/constitution-checks.yaml. Walk every
checks[] entry — the YAML defines id, statement, enforced_by, and
review_question. The set evolves; do not hand-maintain a separate list.constitution-check skill
evaluates the checks where enforced_by includes review (currently:
C-COST, C-LOCAL-CHANGE, C-SINGLE-SOURCE, C-CONFIG-OVER-CODE, C-NO-SPECIAL-CASE,
C-DISCOVERY, C-FILE-SELF-EXPLAINS, C-TESTABLE, C-PORTABLE). Skip rules the
reviewer does not own — the planning-lead evaluates those at plan time.review_question against the diff.
Record: the rule, the file:line where the violation is visible, severity (per
the review severity rubric), and a suggested fix.file:line — what's wrong — why — severity — fix — evidence.enforced_by includes review; planning-lead handles the rest.