AutoGineer
Generated banner for Review Hog Blind Spots General
Generated logo for Review Hog Blind Spots General

Review Hog Blind Spots General

PostHogOfficialPublished by PostHog

  • Skill
  • Review and audit
  • Software development
  • MIT
  • No issues found
Download ZIP

From the author

Checks each chunk for issues the other reviewers missed. Uses their findings to avoid repeating them.
— the description by PostHog

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The blind-spot check acts as the final stage of a multi-perspective code review process. By ingesting the findings of previous specialist reviewers, this agent focuses its analysis exclusively on areas that have not yet been examined. It is designed to uncover complex issues such as unhandled edge cases, failure paths, and cross-file interactions that might have been overlooked by specialized lenses, ensuring a comprehensive final audit of a code chunk.

What it does

  • Analyzes previous review findings to identify areas of focus for other specialists.
  • Targets untested edge cases and error paths ignored by prior reviewers.
  • Evaluates cross-file interactions and assumptions that may break under load.
  • Filters out existing feedback to ensure only new, unique issues are reported.
  • Validates that the code is free of high-value defects not covered by previous audits.

When to use it

  • Use as the final step in a multi-agent code review pipeline.
  • Use when you need to ensure that specialist reviewers have not missed critical blind spots.
  • Use to perform a broad, non-specialized audit of a code chunk after targeted reviews are complete.

Advantages

  • Reduces redundant feedback by explicitly ignoring already reported issues.
  • Increases the depth of code reviews by forcing an investigation into neglected areas.
  • Provides a high-value final check that catches complex, cross-functional bugs.
  • Maintains a high bar for reporting, focusing only on concrete, actionable problems.

Usage examples

“Review this code chunk given the previous findings from the security and performance agents.”
The agent analyzes the provided findings, identifies that edge cases in the error handling logic were missed, and reports a specific potential race condition.
“Perform a blind-spot check on this PR chunk; previous reviewers found no issues.”
The agent conducts a full audit of the code, identifying a logic flaw in the input validation that was overlooked by the initial reviewers.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/posthog/review-hog-blind-spots-general/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip review-hog-blind-spots-general.zip -d .agents/skills

Documentation by PostHog

Blind-spot check

You are the blind-spot check — the final sweep of a PR-chunk review. Several specialist perspectives have each already reviewed this exact chunk in parallel: which ones ran is listed in your review prompt, along with what they found (or a note that they found nothing on this chunk). Your job is to catch the real, high-value issues that ALL of them missed. You are conditioned on their actual output, so hunt where they did not look instead of re-walking their ground.

How to hunt

  • Study the covered findings first (when there are any): they show where the perspectives spent their attention. Your value is everywhere else.

  • Dig into what the prior findings did NOT touch — untested edge cases, error and failure paths, unhandled inputs, cross-file interactions, and assumptions that break under load or hostile input.

  • You are not scoped to one specialty: a real issue is in scope no matter which lens it belongs to, as long as no perspective already raised it.

What to report

  • Only genuinely NEW problems. Do not re-report, restate, or minorly reword anything already covered in the findings above or in the PR's inline comments.

  • The bar is the same as any perspective's: a real, concrete problem with a nameable trigger and a nameable consequence, anchored to this chunk's changes.

  • If the perspectives were thorough and nothing was missed, return an empty issues list. An empty sweep is a valid, good outcome — padding is not.

Files

ATTRIBUTION.md

Attribution

This folder is an unmodified copy of the Agent Skill "review-hog-blind-spots-general", distributed by AutoGineer (https://autogineer.com/agent-skills).

The skill's own files are unmodified copies. AutoGineer is not affiliated with or endorsed by the author or the publisher.

Files added by AutoGineer

  • ATTRIBUTION.md: this file, written by AutoGineer

  • LICENSE: copied from LICENSE

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
PostHog
Publisher
PostHog (Official)
Source
PostHog/skills · skills/omnibus/review-hog-blind-spots-general · commit a5d30e7
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by PostHog.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download review-hog-blind-spots-general.zip