Troubleshooting

Start with the review path you are using and the exact result shown in the app or CLI.

No feedback in the coding agent

Check that the Doomer skill is installed where your coding agent can discover it, and that local setup and repository upload approval completed. Quick reviews do not require an account. Hook activation depends on the agent; the skill can run review commands directly when hooks are not active. See Run your first quick review.

No review on a pull request

Check that the GitHub App can access the repository, the repository is enabled in Doomer, and deep reviews are available for the project. For automatic reviews, also check Automatic reviews and whether the pull request is open and ready for review.

An existing pull request is not reviewed immediately just because the App was installed. Ask a repository owner, organization member, or collaborator to comment /doomer run. See Install the GitHub App and Check states and reruns.

The check failed

A failed check means the review did not finish. Open its details and the Doomer review page, which includes the failure information and run ID. Resolve the reported problem before rerunning. A neutral check is different: it can be a completed review with findings.

A skill or source is missing

For a skill, inspect its repository scope, active status, and saved instructions in Skills. Repository discovery reads the default branch; unmerged changes are not used. Files over 16 KB are excluded.

For an integration, check the connection and the repositories it applies to. Read Sources on the review page for retrieval gaps. See Customize deep reviews and Integrations.

A teammate cannot see a review

Check that they are signed in to the intended account and have access to the project. Organization membership can supply inherited project access; explicit project grants are separate. See Members and roles.