octocode-engineer
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, every claim cited file:line:
- System summary (what/who/invariants) · Control flows (numbered call paths) · Data flows (writers/readers/txn/cache per entity) · Types & protocols (DTOs, schemas, wire contracts, compat)
- Boundaries & ownership (owners, ports, contract tests) · Structure health (folder bloat, file/folder naming, project-fit) · Duplication inventory (near-clones, missing abstraction) · Execution profile (hot paths, async/sync, retries/timeouts/lifecycles)
- Architecture health (per-principle + per-dimension,
confirmed|likely|uncertain) · Clean-code hotspots · Next step (1 sentence)
For a change: change flow, data-flow impact, contract impact, blast radius, risk vector. Safety built in — hard gates stop for your decision before public-contract changes, cross-layer edits, destructive actions, or large blast radius.
How to invoke (user view)
Ask in natural language. The skill activates on phrases like: "understand this codebase", "deep-dive this feature", "review the architecture of X", "why is this slow / flaky / coupled?", "is this PR safe?", "what breaks if I change Y?", "prepare to refactor Z", "validate this RFC against the code".