onboardlisted
Install: claude install-skill devmesh-in/claude-company
# /onboard - adopt an existing codebase (autonomous)
The company adapts to the codebase, not the other way around - and it does the
adapting itself. Everything generated must come from evidence in the repo;
where you infer, mark confidence. Ask the owner nothing; report findings with
veto rights at the end.
## 0. Verify the drop-in
`company/METHOD.md` and `.claude/hooks/` must exist (installer ran).
## 1. Audit (Explore agents, parallel)
1. **Architecture recovery**: languages, frameworks, entry points, module
map, data stores, external services, how pieces talk. One page, with paths.
2. **Conventions mining**: the unusual, opinionated, tribal things that
prevent agent drift - naming quirks, error-handling patterns, forbidden
practices visible in code. Skip the generic.
3. **Machinery discovery**: real test/lint/typecheck/build/dev/migrate/seed
commands from scripts, Makefiles, CI configs - verified runnable.
4. **Load-bearing surfaces**: single writers, state machines, money/ledgers,
auth seams, shipped migrations, generated code.
## 2. Wire it (you, from evidence, no approval gates)
- **Gates**: `python3 .claude/hooks/gates_detect.py --write`, then reconcile
with the audit's findings (CI configs often know gates detection cannot
see). Run `bash company/run-gates.sh` and record the honest result - gates
that are red TODAY go into STATUS as the existing-debt baseline, not
silently into the config as passing.
- **Frozen surfaces**: apply the opini