Docs
Start with the workflow.
These docs are organized like an SOP: get installed, set up provider keys, run the plan-to-commit loop, then dig into security and reference material only when you need it.
First 10 minutes
Quickstart
Install, authenticate, initialize a repo, and run the first review.
SOP: plan to commit
The canonical operating procedure from requirement to committed review trail.
VS Code chat
Use @almightygpt /auth, /review, /precommit, and /runs from the editor.
Auth setup
Store provider keys safely in the OS keychain or VS Code SecretStorage.
The command path
AlmightyGPT is easiest to understand as one repeatable path. You can run it from the terminal, VS Code commands, or VS Code Chat, but the artifact trail is the same.
Canonical SOP
> almightygpt plan --topic checkout-hardening --text "tighten checkout flow"> almightygpt review --plan docs/claude-plans/checkout-hardening.md --reviewer codex --topic checkout-plan> npm test> almightygpt review --diff --worker claude --reviewer codex --topic checkout-hardening> almightygpt precommit --strict> almightygpt decide latest --status approved --note "ready to ship"> git commit -m "Harden checkout flow"SOP checklist
- Plan the requirement
- Review the plan
- Build the change
- Run local tests
- Review the diff
- Run precommit
- Record the decision
- Commit the trail
What should be committed
Commit the human-facing plan/review/precommit Markdown files when they explain an engineering decision. Keep `.almightygpt/runs/` local unless your team intentionally changes that policy.