菜单
Produce a read-only structural audit of the Contraponto codebase — class responsibilities, package boundaries, duplication, and rule compliance. Use when the user asks for an architecture review or structural audit; does not change code.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | review-code-structure |
| description | Produce a read-only structural audit of the Contraponto codebase — class responsibilities, package boundaries, duplication, and rule compliance. Use when the user asks for an architecture review or structural audit; does not change code. |
You are a senior Java architect reviewing the Contraponto codebase. Produce a read-only structural audit — do not change code unless the user explicitly asks to fix findings afterward.
Prerequisites: Read ARCHITECTURE.md and docs/domain-specification.md before auditing.
Default: full repository (src/main/java/dev/vepo/contraponto/, templates, tests).
If the user names a package or path, restrict scope but still check cross-package imports.
Write one report:
reports/code-structure-review-{sequential}-{dd-MM-yyyy-HH-mm-ss}.md
Severity: critical | major | minor | suggestion.
Do not ask for confirmation before starting. Do not apply refactors in this skill.
*Access, observers.Read contraponto-layered-architecture.mdc.
| Check | Pass criteria |
|---|---|
| Endpoint → Repository bypass | Endpoints with business logic use *Service |
| Service → EntityManager | Services use repositories, not EM directly |
| Repository purity | No business rules or HTTP in repositories |
Read contraponto-bounded-contexts.mdc.
shared kernel does not import feature contextsBoundedContextRulesTest would passRead contraponto-tell-dont-ask.mdc, contraponto-law-of-demeter.mdc.
Read contraponto-core.mdc, contraponto-no-method-bypass-allowed.mdc.
*Paths / TemplateExtensions.url — not hardcoded routes*Access)components/# Code structure review — Contraponto
## Summary
(2–3 sentences)
## Findings
### Critical
- ...
### Major
- ...
### Minor / suggestions
- ...
## Recommended next steps
1. ...
Start the audit now.
Automatically raise JaCoCo test coverage to 80% (instruction and branch) in this Quarkus/Java project while ensuring every test asserts all results. Use when the user asks to increase test coverage or close coverage gaps.
Run local static analysis (no SonarCloud token) on this Quarkus/Java project and fix findings with conservative, behavior-preserving changes. Use when the user asks to fix static analysis issues, lint warnings, or Sonar-style findings without calling SonarCloud.
Automatically fix all failing Maven tests in this Quarkus/Java project by iterating until they pass. Use when the user asks to fix failing tests or get the test suite green.