Quick vs. deep reviews

Questions inside your coding agent’s loop in seconds; independent PR reviews in minutes.

Quick vs. deep reviews

Quick reviews question your coding agent whenever it edits. Deep reviews independently investigate the change and can start before a PR exists. Both tracks can continue through PR feedback and further edits.

Quick reviews

Seconds · Inside your coding agent

  1. 1

    Agent edits

    Your coding agent works on the change.

  2. 2

    Doomer questions

    The skill returns hypotheses about the latest edits.

  3. 3

    Agent decides

    Accept, reject, or defer. Your agent chooses how to act.

  4. 4

    Doomer records

    The response is saved so the next edit gets fresh suggestions.

Repeats with each edit, including edits prompted by PR feedback.

Deep reviews

Minutes · Independent model and review engine

  1. 1

    Start a deep review

    Before the PR, or on an existing pull request.

  2. 2 · Build context in parallel

    • Collect sources
    • Determine intent
    • Identify attack paths
    • Inspect provenance
  3. 3

    Independent investigations

    A separate model and review engine investigate the change.

  4. 4

    Review the findings

    Evaluate the findings and their supporting evidence.

  5. 5

    Post feedback to the PR

    Share the resulting findings in the pull-request review.

PR creation is a milestone. Both review tracks can continue as the code changes.

Quick reviews help the coding agent question its next decision. Deep reviews give the change a separate investigation.
Quick reviewsDeep reviews
Where it runsInside your coding agent’s work loop and harness, including edits from PR feedbackIndependently of the coding agent, before the PR and on the PR
Who reviewsYour coding agent investigates and makes the final decisionA separate generative model and review engine investigate independently
How longSecondsMinutes
What you getQuestions and suggestions for your agent to look closerFindings with supporting evidence and repository context
Where to startInstall the Doomer skill in your coding agentInstall the GitHub App and enable a repository
Where feedback appearsYour coding conversation or a review linkGitHub checks and review comments, plus the Doomer review page

I want feedback while coding

Install the Doomer skill, then run your first quick review. The skill guides setup and brings feedback into your task. Quick reviews through the skill do not require an account.

I want a review on a pull request

A deep review gathers sources, determines intent, identifies attack paths, and inspects provenance. The independent engine investigates the change, reviews its findings, and posts feedback to the PR.

Install the GitHub App, enable your repository, then run your first deep review. You can start here without installing the coding-agent skill.

I want both

Use quick reviews to give your coding agent questions whenever it edits. The agent investigates, decides whether a concern is valid, and chooses what to change. Deep reviews provide an independent assessment and can start before the PR exists. After the PR is created, deep reviews also work like a traditional PR reviewer. When review feedback leads to more edits, quick reviews run in the agent’s loop again.

To change the guidance used by deep reviews, see Customize deep reviews. These review instructions serve a different purpose from the Doomer skill installed in your coding agent.