Customize deep reviews
Review skills are saved instructions that guide Doomer's deep reviews. Use them for conventions or checks that matter to your project, such as how an API enforces account access or which migration patterns your team supports.
The Doomer skill for coding agents runs reviews during a coding task. The skills on this page customize what a deep review considers.
Add guidance to a project
Open Skills in your Doomer project. Project owners and admins can manage skills; other members can read them.
Choose one of these starting points:
- Recommended or the Catalog: read a skill's instructions, then install it with the repository scope and update policy you want.
- Import skill: supply a GitHub file URL for an existing skill.
- Create skill: write your own instructions. Describe the behavior to check and give concrete examples of acceptable and problematic code.
- Detected: inspect skill files and repository instructions discovered in an enabled GitHub repository. Choose a repository and Detect repository skills to scan again.
For example, a useful instruction is: “Every invoice lookup must constrain both invoice ID and account ID. Check the caller and query together.” This gives the reviewer a specific property to investigate.
Use repository instructions
Doomer discovers supported skill files and AGENTS.md instructions on the repository's default branch. Unmerged changes to those files in a pull request are not activated for that review.
Skills under .doomer/skills/<name>/SKILL.md are enabled by default when discovered. Other detected skills and AGENTS.md instructions need to be enabled explicitly. Inspect the instructions before activating them. Detected skills stay scoped to their source repository.
Files larger than 16 KB are excluded and shown as Too large — not included. Shorten the source file and detect it again.
Choose scope and updates
Open a skill's Settings. Applies to selects one repository or all repositories in the project for installed skills. Review status activates or pauses the skill. Changes apply to future review attempts.
| Update policy | Behavior |
|---|---|
| Read only | Keeps the saved version fixed |
| Continuous sync | Follows upstream exactly, replacing local edits; checks for updates every 15 minutes |
| Doomer managed: propose updates | Merges source changes with your edits and proposes changes for approval |
| Doomer managed: merge automatically | Applies merges without conflicts; conflicts still require approval |
Doomer-managed skills scoped to a repository can also learn from explained review feedback for that repository. Review proposed changes before applying them.
Editing imported or detected instructions in Doomer creates a project override. It does not write to the original file or update other copies of that skill.
Verify the guidance
Check that the skill is active and applies to the repository, then request a new deep review. A skill guides the investigation; it does not guarantee a finding or replace your tests. Use review feedback to explain where the review got a rule right or wrong.