/audit
Have an existing codebase? Run it — you get the detected stack, a gap list with severity and file:line evidence, a task per gap, and a PROJECT.md. Same as `/start audit`.
> /plugin marketplace add avelikiy/great_cto> /plugin install great_cto@great-cto
Command definition
audit.mddescription: "Have an existing codebase? Run it — you get the detected stack, a gap list with severity and file:line evidence, a task per gap, and a PROJECT.md. Same as `/start audit`."
argument-hint: "[optional: 'eval' | 'lint' | focus area, e.g. 'focus on security']"
user-invocable: true
allowed-tools: Read, Write, Bash, Glob, Grep, Agent
model: sonnet
`/audit` is an alias: **same as `/start audit`**. The audit lives in one place — the `## Path: audit` section of the `/start` command — so the two can never drift apart.
Run it
1. Read the `/start` command file — the plugin's `commands/start.md`:
PD=${CLAUDE_PLUGIN_ROOT:-$(ls -d ~/.claude/plugins/cache/*/great_cto/*/ 2>/dev/null | awk -F'/plugins/cache/' '{split($NF,p,"/"); print p[3], $0}' | sort -V | tail -1 | cut -d' ' -f2- | sed 's|/$||')}
for F in "$PD/commands/start.md" "$HOME/.claude/commands/start.md"; do
[ -f "$F" ] && { echo "START_MD=$F"; break; }
done2. Jump to `## Path: audit` and follow it to the end, with this command's whole argument as "the audit argument":
| You typed | Runs | |-----------|------| | `/audit` | `/start audit` — full audit | | `/audit eval` | `/start audit eval` — eval harness | | `/audit lint` | `/start audit lint` — anti-pattern scan of artefacts | | `/audit focus on security` | `/start audit focus on security` |
Do NOT run the new-project guards or Steps 0–6 of `/start` — only the audit path.
Read more
description: "Have an existing codebase? Run it — you get the detected stack, a gap list with severity and file:line evidence, a task per gap, and a PROJECT.md. Same as `/start audit`." argument-hint: "[optional: 'eval' | 'lint' | focus area, e.g. 'focus on security']" user-invocable: true allowed-tools: Read, Write, Bash, Glob, Grep, Agent model: sonnet
`/audit` is an alias: **same as `/start audit`**. The audit lives in one place — the `## Path: audit` section of the `/start` command — so the two can never drift apart.
Run it
1. Read the `/start` command file — the plugin's `commands/start.md`:
PD=${CLAUDE_PLUGIN_ROOT:-$(ls -d ~/.claude/plugins/cache/*/great_cto/*/ 2>/dev/null | awk -F'/plugins/cache/' '{split($NF,p,"/"); print p[3], $0}' | sort -V | tail -1 | cut -d' ' -f2- | sed 's|/$||')}
for F in "$PD/commands/start.md" "$HOME/.claude/commands/start.md"; do
[ -f "$F" ] && { echo "START_MD=$F"; break; }
done2. Jump to `## Path: audit` and follow it to the end, with this command's whole argument as "the audit argument":
| You typed | Runs | |-----------|------| | `/audit` | `/start audit` — full audit | | `/audit eval` | `/start audit eval` — eval harness | | `/audit lint` | `/start audit lint` — anti-pattern scan of artefacts | | `/audit focus on security` | `/start audit focus on security` |
Do NOT run the new-project guards or Steps 0–6 of `/start` — only the audit path.
You already have the agent. This is everything around it. great_cto runs Claude Code as a pipeline of 70 specialist agents — an independent model checks each stage before the next builds on it, spending caps refuse rather than warn, and three decisions stay yours: what gets built, how, and whether it ships.
Other commands on great-cto.
More commands from other plugins.
build
CommandImplement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.

