Skip to main content
Focused agents extend the core review with checks for a specific engineering concern. Use them when one type of risk recurs in a repository. Examples can include checks for:
  • dependency risk
  • code complexity
  • test coverage changes
  • public code documentation
  • frontend bundle size
  • license policy
  • N+1 query patterns
  • accessibility issues

​
Choose a focused check

Enable a focused check when:
  • the repository uses the relevant framework or package ecosystem
  • maintainers agree on the expected behavior
  • the finding can be verified from code or build output
  • the expected signal is worth the additional review volume
Avoid enabling every available check at once. Start with the repository’s highest-risk area, review the output, and expand gradually.

​
Focused agents and custom rules

Use a custom rule for an organization-specific standard written in natural language. Use a focused agent for a specialized analysis domain such as dependency auditing or accessibility. Use codebase scans when you need a broader repository-wide assessment.