Review system architecture, simplify boundaries, or compare interface designs from repository evidence
60
70%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/octopus-architecture/SKILL.mdHost: Codex CLI — This skill was designed for Claude Code and adapted for Codex. Cross-reference commands use installed skill names in Codex rather than
/octo:*slash commands. Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it. For host tool equivalents, seeskills/blocks/codex-host-adapter.md.
Load skills/blocks/engineering-method-selection.md from the installed plugin
and apply only the methods relevant to this task. Preserve this entry point's
execution contract and output format. Read referenced skills as instructions;
do not invoke the current command recursively or add provider calls from a seat.
Run this method on the current host. A routine architecture review makes zero additional provider dispatches.
--peer-review, an explicit independent-review
request, or an existing risk policy may add one bounded external reviewer through
Octopus routing. Report incomplete independent coverage if that reviewer cannot
read the source or does not return a grounded contribution.
Read and apply skills/blocks/architecture-simplification.md from the installed
plugin root. Pin the source revision and inspect implementation, callers, tests,
recent churn, and failure behavior before recommending a boundary.
For a single simplification, produce one evidence-backed interface. For a design choice, produce two alternatives from the same immutable requirements:
Label two host-generated drafts as correlated alternatives from one model. If an independent reviewer is authorized, send it the same source and requirements but not Draft A before its first response. Transport diversity does not prove model family diversity. Unknown family means unknown independence.
Return Evidence, Caller contract, Proposed interface, Migration, Test impact, and Decision. The decision is keep, simplify, or investigate.
simplify requires exact source evidence and a concrete caller example. A design
review never authorizes an automatic refactor.
When the host exposes language-server tools, use document symbols, workspace symbols, definitions, and references to confirm module boundaries and caller relationships before proposing an interface. Treat LSP results as an index: verify consequential claims against source and tests, and fall back to repository search when the language server is unavailable or incomplete.
Adapted from codebase-design and DESIGN-IT-TWICE in mattpocock/skills at
commit 3cca18b368ae95cdbdebbff572ccafa662551015 under the MIT License. See
THIRD_PARTY_NOTICES.md.
805d58c
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.