Run your first quick review
Start here with a repository open in Codex or Claude Code. Install the skill once, then give your agent a normal coding task. Quick reviews do not require a Doomer account.
Supported in terminal/TUI and graphical UI sessions, locally or remotely, on macOS and Linux.
No account required does not mean no data is processed. After upload approval, Doomer receives source snapshots, task context, and the agent’s finding responses. Treat review links as private. Read about uploads, link access, and retention.
1. Install the Doomer skill
Install the Doomer skill
Free · No account required
Open your repository in Codex or Claude Code, then paste this into your agent.
Read https://doomer.ai/install.md and follow the instructions to set up Doomer in this repository.Run this in your terminal to install Doomer for Codex and Claude Code across repositories.
npx skills add doomerlabs/skills --skill doomer-review --global --agent codex claude-code --yesOpen a fresh Codex or Claude Code session in a repository and ask your agent to finish Doomer setup.
For your team, choose a repository installation and commit the generated skill files. Teammates get the skill when they clone or pull. Once installed, the agent detects it automatically.
Team use is optional. Teammates can opt out locally while the shared skill stays in the repository.
Already installed? Go straight to the next step. For manual installation or personal setup, see all installation options.
2. Give your agent a normal coding task
Ask the agent to fix a bug or build a small feature in the repository. Codex and Claude Code detect the installed skill and use it automatically. You do not need to invoke Doomer or ask for a review.
If local setup or repository upload approval is needed, the agent guides you through it. Each teammate decides whether to allow Doomer in their own agent, even when the skill is committed to the repository.
The skill installs and uses the Doomer CLI behind the scenes. You do not need to run review commands yourself. Review processing uses uploaded source snapshots on Doomer’s hosted service.
3. Watch the first review
As the agent edits, the skill requests a quick review. In seconds, Doomer sends back hypotheses: possible concerns and focused checks for the agent to investigate.
The agent decides whether to accept, reject, or defer each suggestion, and sends its decision and explanation back to Doomer. Your coding agent remains the reviewer and makes the final decision about how to act.
Open the quick review link from the coding session to see the hypotheses and recorded responses. If a response is still pending, the page shows that the agent has not responded yet.
Confirm that it worked
You’re ready when…
- The agent returns a quick-review link, and the review of your latest changes has completed.
- Each hypothesis has an accept, reject, or defer decision and an explanation in Feedback. A completed review can also return no hypotheses.
- If using hooks, Doomer has received a real callback from this session. Until then, the skill can submit reviews explicitly; installed hooks alone do not prove activation.
An example from concern to recorded response
1. Doomer asks
Can this lookup return no record?
Check whether the handler reads the account’s name before handling a missing account.
2. Your agent investigates
“The lookup returns null for an unknown ID. I added a not-found response before reading the name, and the missing-account test passes.”
3. The response is recorded
Accepted · fixed
The review’s Feedback view shows the agent’s explanation. The agent submits the updated code for another review.
Supported environments
| What you use | Supported |
|---|---|
| Coding agent | Codex or Claude Code |
| Interface | Terminal/TUI or graphical UI |
| Where the agent runs | Your local machine or a remote coding environment |
| Operating system | macOS or Linux |
Install the skill and its CLI in the environment where the agent edits the repository. A local desktop installation does not install the runtime in a remote environment. If you choose to allow Doomer, complete any needed setup and upload approval in that environment.
Team use and opting out
You can commit the skill without requiring every teammate to use Doomer. The committed files share instructions; they do not share credentials, install tools on other machines, or grant upload permission for other developers.
A teammate who does not want Doomer can tell their agent:
Do not use Doomer in this chat. If a Doomer review task is already active, pause it. Leave the repository's shared skill files unchanged.That choice applies to their session and does not disable Doomer for anyone else. They can keep an ongoing opt-out instruction in their personal agent configuration. They do not need to remove or edit the committed skill.
They can also decline local setup or repository upload approval. Sharing the skill is separate from each developer's choice to enable it.
Keep working
Several quick reviews during one task are normal. Each new edit is another opportunity to question an assumption before the agent builds more code around it. Doomer records the agent’s responses so the same suggestions do not keep returning after the next edit.
When the work is done, the agent can finish the turn and move toward a PR. Edits made later in response to PR feedback can start the quick-review loop again.
See the complete review-and-response cycle, or compare quick and deep reviews. Deep reviews provide an independent investigation and can begin before the PR exists.