القائمة
Use when reviewing Wort-Werk code, diffs, or implementation details for consistency across modules, naming, layering, testing patterns, and repository conventions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use when reviewing Wort-Werk design proposals, implementation plans, ADR changes, repository-level direction, or refactors that affect boundaries, layering, or long-term structure.
Use when reviewing Wort-Werk authentication, sessions, CSRF, database access, containers, OCI deployment, secrets, or any change with confidentiality, integrity, or availability risk.
استنادا إلى تصنيف SOC المهني
| name | project-coherence-review |
| description | Use when reviewing Wort-Werk code, diffs, or implementation details for consistency across modules, naming, layering, testing patterns, and repository conventions. |
Use this skill for reviewing code, uncommitted changes, or completed implementations where the main question is whether the change stays coherent with the rest of Wort-Werk.
Do not use this skill as the primary lens for repo-direction or ADR-level design questions. Use architecture-review when the change affects system direction, layering strategy, or long-term design.
Before reviewing the change, read:
AGENTS.mddocs/spec/docs/tasks/If the spec/task/ADR trail does not support the implementation, call that out explicitly.
./mvnw clean verify as the commit gateCheck whether the change:
Prefer one coherent project-wide approach over locally convenient exceptions.
Be especially alert for:
Specs, tasks, and ADRs remain the source of truth. This skill helps judge coherence against them and against the current codebase.