← ClaudeAtlas

todou-clilisted

todou CLI quick reference — issue/comment/attach/watch commands, cursor semantics, status-flow conventions, and the rules for how agents interact with the tracker. Read this first before touching a todou tracker.
orzFly/todou · ★ 1 · AI & Automation · score 74
Install: claude install-skill orzFly/todou
# todou CLI todou is the team's issue tracker. Agent questions, reports, deliverables, and reviews all go through the tracker so everything leaves a trace. Project-specific facts (slug, server, sandbox project, deploy command) live in the host project's CLAUDE.md / memory; `<proj>` below is a placeholder. ## Basics - Just run `todou` — the CLI config auto-selects the machine-account profile prepared for agents; no login flags needed. - **Every todou command needs network access**: sandboxed runs get their sockets denied, so always run them with the sandbox disabled. - `--json` gives structured output; `todou api <method> <path>` covers anything the CLI lacks. - If the deployment has a sandbox project (scratch space), run experiments and guinea-pig tests there — never pollute the real tracker. ## Command cheat sheet ```bash todou issue list -p <proj> [--open|--closed|--status X|--unread|-q text] todou issue view 16 -p <proj> # prints a cursor at the end, for watch --since todou issue create -p <proj> --title T [--body-file f] [--status Next] # ^ when filing on behalf of the user, quote their original words verbatim # in the body (if any) — off-tracker requests have no other trace todou issue edit 16 --status "In Progress" # status/title/labels/assignees todou issue close 16 --comment "done" todou comment add -p <proj> 16 --body-file f # long bodies: --body-file /dev/stdin <<'EOF' todou attach -p <proj> 16 file.png ... # mime inferred from the extens