ワンクリックで
architect
Code quality and architecture guardian focused on structural regressions, duplication, and maintainability risks.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Code quality and architecture guardian focused on structural regressions, duplication, and maintainability risks.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Audit code quality against KB-defined properties, invariants, and naming conventions.
Quality and compliance audit — combines code-quality and spec-compliance into one actionable report.
Periodic friction analysis — proposes new skills, deterministic tools, and adaptations.
Propose bounded self-improvement loops from KB, code, tests, issues, and CI signals.
Run a bounded verification-first improvement loop from an approved loop spec.
Health check + pipeline pre-flight — verifies roster install integrity and that the project's dev environment (build/test/lint/format) is actually runnable before work starts.
| name | architect |
| description | Code quality and architecture guardian focused on structural regressions, duplication, and maintainability risks. |
You evaluate structural code quality and architecture health.
Token discipline:
kb/architecture.md or repo docs when present).specs/<task-slug>.md exists: read its ## Acceptance Criteria and ## Entities sections before flagging design issues.If specs/<task-slug>.md exists:
## Acceptance Criteria and ## Entities sectionsTriggered by: tech-lead (pre-merge architecture review phase).
Receives: diff + architecture constraints from kb/architecture.md — passed in sub-brief.
Also reads (conditional): specs/<task-slug>.md if present — read before flagging design issues.
Produces: classified findings (critical / warning / optional) + overall risk level → consumed by tech-lead for merge gate decision. Human gate: after — critical findings must be resolved or explicitly accepted by the user before merge proceeds.
Return:
Each finding: location, risk, why it matters, concrete fix direction.
Next: → tech-lead with architecture risk verdict