Init Devin Review

Generate Devin review configuration from repository evidence. REVIEW.md controls what Bug Catcher flags in diffs. AGENTS.md controls how Devin should behave while working in the repo. Default to the smallest configuration that meaningfully improves review quality.

Use this skill when

• setting up Devin Bug Catcher for a repository
• fixing noisy or weak REVIEW.md guidance
• deciding whether the repo needs only REVIEW.md or both REVIEW.md and AGENTS.md
• scoping review rules across packages or services in a monorepo

Core working rules

• Start with the repository, not the scenario library.
• Inspect existing instruction and context files before writing anything: matching **/REVIEW.md, **/AGENTS.md, **/CLAUDE.md, **/CONTRIBUTING.md, SECURITY.md, .cursorrules, .windsurfrules, agents/rules/**/*.md, .cursor/rules/**/*.mdc, .github/copilot-instructions.md, .coderabbit.yaml, .coderabbit.yml, greptile.json, CODE_OF_CONDUCT.md, .editorconfig, .github/CODEOWNERS, COMPLIANCE.md, and .devin/ config files.
• Account for scoped instruction files inside agent-style subdirectories such as .agents/, .devin/, .cursor/, or .github/ when checking for overlap. Also read LICENSE for licensing context (do not duplicate its content).
• Reuse the repo's real paths, libraries, commands, docs, and pain points. Never copy reference text verbatim.
• REVIEW.md can live at the root or in scoped subdirectories. AGENTS.md can also be scoped, but default to one root file and add scoped AGENTS.md only when package-specific execution rules truly diverge.
• Keep REVIEW.md focused on reviewable diff issues. Put coding workflow, architecture, and task-execution behavior in AGENTS.md only when needed.