overseer

Review code diffs and pull requests with structured checklists and remediation steps.

11|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/brolag/neural-claude-code --skill overseer-brolag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: overseer
Source: https://github.com/brolag/neural-claude-code/tree/main/skills/overseer
Command: npx skills add https://github.com/brolag/neural-claude-code --skill overseer-brolag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewing code diffs and PRs manually is error-prone and time-consuming; Overseer automates quality checks to detect slop, security issues, and inconsistencies before merges.

Core Features & Use Cases

  • Slop detection: identify duplicated code, dead code, and vague naming.
  • Security checks: flag potential vulnerabilities and unsafe patterns.
  • Consistency & best practices: ensure adherence to project guidelines, tests, and documentation.
  • Use Case: integrate with PR workflows to provide automated review reports and actionable fixes.

Quick Start

Run /overseer to start a quick review of the current branch.

Frequently Asked Questions about overseer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review and quality checks before merging a pull request?

Automating code review before merging a pull request requires analyzing diffs to detect duplicated code, security vulnerabilities, and guideline inconsistencies. This process generates a structured checklist with scoring and concrete remediation steps.

What is the best way to detect duplicated code, dead code, and security issues in a PR diff?

To detect duplicated code and security issues in a PR diff, automated review mechanisms flag unsafe patterns and vague naming. They apply best practice checks to the codebase and output a formatted report with actionable fixes.

Can I apply automated diff review to multiple files or specific pull requests?

Yes, automated diff review can be applied to multiple files or specific pull requests. The review processes the targeted code changes against project guidelines, enforcing security checks and consistency before generating a structured quality report.

How do I enforce project guidelines and best practices during PR review?

To enforce project guidelines during PR review, automated checks analyze code diffs for adherence to documentation and testing standards. This ensures consistency across the codebase and provides a scoring checklist for concrete remediation.

Does automated PR review provide actionable remediation steps for security vulnerabilities?

Yes, automated PR review provides actionable remediation steps for security vulnerabilities. It flags potential unsafe patterns during diff analysis and includes concrete fixes within a formatted report to resolve issues before merge.

When should I not use automated code review for my pull requests?

Automated code review should not be used as the sole validation for complex architectural changes, as it primarily targets slop detection, security patterns, and guideline consistency rather than deep functional logic or business requirements.