What is Review Code Structure?

A read-only audit of how a Java project’s code is organized. It checks class responsibilities, package boundaries, duplicated code, and compliance with the project’s architectural rules.

Use it to inspect the project’s Java and web code, including feature packages, endpoints, repositories, services, entities, request and response types, and violations of the layered architecture.

Poor boundaries and duplicated responsibilities make software harder to change and can cause layers to depend on the wrong parts of the system. The audit records these structural issues without modifying code.

Review Code Structure — Command by vepo

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/vepo/issues/review_code_structure

Clone the repo

git clone --depth 1 https://github.com/vepo/issues

Made for: Cursor.

Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 536 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00019	$0.00536
Opus 5	$0.00010	$0.00268
Sonnet 5	$0.00004	$0.00107
Haiku 4.5	$0.00002	$0.00054

Measured yesterday against content hash d51557304f95, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Review Code Structure scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/commands/review_code_structure.md · 92 lines

How it starts

The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior Java architect reviewing the Issues 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.

Scope

Default: full repository (src/main/java/dev/vepo/issues/, src/main/webui/, tests).

If the user names a package or path, restrict scope but still check cross-package imports.

Output

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 command.

Phase 1 — Inventory

List feature packages from ARCHITECTURE.md §5.
Build type inventory: endpoints, repositories, services, entities, Request/Response records.

Phase 2 — Layer compliance

Read issues-layered-architecture.mdc.

Check	Pass criteria
Endpoint → Repository bypass	Endpoints with multi-entity logic use `*Service`
Service → EntityManager	Services use repositories, not EM directly
Repository purity	No business rules or HTTP in repositories

Phase 3 — HTTP contract

Read issues-http-contract.mdc.

All *Request/*Response are records
ArchitectureTest would pass

Phase 4 — Bounded contexts

Read issues-bounded-contexts.mdc.

Package dependency direction matches domain spec
No unrelated cross-package repository access

Phase 5 — Duplication

Repeated ticket/workflow validation logic
Duplicate Angular HTTP calls
Similar Response mapping patterns

Phase 6 — Frontend structure

Services centralize API calls
Components stay presentation-focused

Report template

# Code structure review — Issues

## Summary
(2–3 sentences)

## Findings

### Critical
- ...

### Major
- ...

### Minor / suggestions
- ...

## Recommended next steps
1. ...

Read the full file on GitHub · 92 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 92 lines · 19 tokens per session scan A d51557304f95

Subscribe to this mod's changes

Review Code Structure is a command published in the GitHub repository vepo/issues (8 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 536 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review Languages Planning angular java quarkus

Review Code Structure

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Scope

Output

Phase 1 — Inventory

Phase 2 — Layer compliance

Phase 3 — HTTP contract

Phase 4 — Bounded contexts

Phase 5 — Duplication

Phase 6 — Frontend structure

Report template

What this file has done since we first saw it

Other commands, from other repositories

plan

wire-harness

build

ship

onboard

review