Octocode Engineer

Understand, change, and verify a codebase with system awareness. Single-file reading misses root causes — they live in boundaries, flow ownership, contracts, data paths, and runtime assumptions. This skill makes those visible before you act, and keeps them verified after.

What you get (user view)

A structured understanding artifact, grounded in evidence, with every claim cited by file:line:

• System summary — what it does, who consumes it, invariants.
• Control flows — numbered call paths for the critical features.
• Data flows — writers, readers, transaction boundaries, caches per entity.
• Types & protocols — authoritative DTOs, schemas, wire contracts, compatibility posture.
• Boundaries & ownership — who owns what, where ports live, which tests prove contracts.
• Duplication inventory — top near-clones and the missing abstraction.
• Execution profile — hot paths, async/sync posture, retries/timeouts/lifecycles, runtime risks.
• Architecture health — one line per Clean-Architecture principle and per analytic dimension, with confirmed|likely|uncertain.
• Clean-code hotspots — top findings worth fixing.
• Next step — one sentence.