Menú
Strict maintainability review: abstraction quality, file size, spaghetti growth, code-judo simplification. Trigger: 'deep quality review', 'thermo-nuclear review', 'harsh maintainability audit'.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Run objective, repeatable improvement work under an immutable verifier and hard iteration, cost, time, and no-progress limits. Use for approved experiments with an automated metric and sandboxed worker.
Write concise, calm technical responses whose structure matches the decision, evidence, or sequence being communicated. Use when drafting substantial plans, reviews, findings, documentation, or completion summaries.
Operate inside a ControlKeel-governed session. Use this before code edits, shell execution, delegation, deploy work, or any task that needs CK validation, findings, budget, proof, or routing context.
Keep a governed session within budget. Use this before long-running agent work, bulk processing, or any task where spend pressure could change the plan.
Close a governed work session with validation, proof, findings, budget, digest, learning, and handoff checks. Use when the user asks to wrap up, stop for the day, or leave work ready for another agent.
Audit tests that may pass without proving the claimed behavior. Use for periodic test-quality reviews or when coverage looks healthy but regressions still escape.
| name | deep-code-quality-review |
| description | Strict maintainability review: abstraction quality, file size, spaghetti growth, code-judo simplification. Trigger: 'deep quality review', 'thermo-nuclear review', 'harsh maintainability audit'. |
| when_to_use | Activate ONLY when explicitly asked for a harsh code quality review. Do NOT auto-trigger during normal coding or security reviews. |
| argument-hint | [file, PR, branch, or area] |
| disable-model-invocation | true |
| license | Apache-2.0 |
| compatibility | ["opencode-native","claude-standalone","cursor-native","codex"] |
| metadata | {"author":"controlkeel","version":"1.1","category":"quality","ck_mcp_tools":["ck_validate","ck_finding","ck_git_diff","ck_review_submit"],"related_skills":["security-review","parallel-review"]} |
Extremely strict maintainability review. Be ambitious about structure — search for "code judo" moves that make the implementation dramatically simpler.
security-review)ck_finding rule code_quality.file_size (severity high).code_quality.spaghetti_condition.code_quality.unnecessary_abstraction.code_quality.type_boundary.code_quality.wrong_layer.code_quality.orchestration.Additional rules: code_quality.missing_abstraction, code_quality.magic_handling, code_quality.duplicate_logic.
ck_git_diff to get changes. Run ck_validate for automated patterns.ck_finding using the rule IDs above.ck_review_submit (review_type: plan). Wait for approval.No approval unless: no structural regression, no missed simplification, no file explosion, no spaghetti growth, no unnecessary abstraction, no layer leak, no missed decomposition.
parallel-review to run both concurrently.ck_finding records with specific rule IDsck_review_submit plan with prioritized findings