AutoGineer
Generated banner for Incident Response Code Reviewer
Generated logo for Incident Response Code Reviewer

Incident Response Code Reviewer

Seth HobsonCommunityCreated by Seth Hobson

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

From the author

Reviews code for logic flaws, type safety gaps, error handling issues, architectural concerns, and similar vulnerability patterns. Provides fix design recommendations.
— the description by Seth Hobson

AutoGineer summary

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

The incident-response-code-reviewer acts as a technical auditor for software projects. It systematically evaluates codebases to uncover logic errors, type safety deficiencies, and inadequate error handling. Beyond simple bug detection, it analyzes architectural patterns to identify coupling issues and layering violations, while providing structured, severity-rated feedback and design recommendations for remediation.

What it does

  • Performs deep analysis of code paths to detect logic flaws and incorrect algorithmic assumptions.
  • Audits error handling mechanisms to ensure robust failure management.
  • Evaluates type safety and suggests improvements to prevent runtime errors.
  • Identifies architectural concerns such as tight coupling or missing abstractions.
  • Detects recurring vulnerability patterns across the codebase.
  • Provides structured review reports with severity ratings and fix design recommendations.

When to use it

  • During pre-deployment code reviews to ensure quality and security.
  • When investigating recurring bugs or logic flaws in a production codebase.
  • When refactoring legacy code to improve architectural integrity.
  • To validate input handling and contract enforcement in critical modules.

Advantages

  • Provides actionable, minimal-impact fix designs rather than just identifying problems.
  • Helps maintain consistent architectural standards across the project.
  • Reduces technical debt by catching logic and type safety issues early.
  • Standardizes the review process with structured severity ratings.

Usage examples

“Review this authentication module for logic flaws and error handling gaps.”
The agent provides a structured report highlighting missing edge cases in token validation, suggests adding specific try-catch blocks, and proposes a more robust input validation strategy.
“Analyze this service for architectural coupling and suggest a refactoring path.”
The agent identifies tight coupling between the data layer and the business logic, recommending specific abstractions to decouple the components and improve testability.

Install

  1. Download the subagent as a ZIP:

    https://autogineer.com/agent-skills/wshobson/incident-response-code-reviewer/download

  2. Extract the subagent file into .claude/agents in your project (use ~/.claude/agents for every project):

    mkdir -p .claude/agents && unzip -j incident-response-code-reviewer.zip 'incident-response-code-reviewer/code-reviewer.md' -d .claude/agents

  3. Keep the LICENSE and ATTRIBUTION.md files from the ZIP with your copy.

Documentation by Seth Hobson

You are a code review specialist focused on identifying logic flaws and design issues in codebases.

Purpose

Perform thorough code reviews to find logic errors, type safety gaps, missing error handling, and architectural concerns. You identify similar vulnerability patterns across the codebase and recommend minimal, effective fixes.

Capabilities

  • Logic flaw analysis: incorrect assumptions, missing edge cases, wrong algorithms

  • Type safety review: where stronger types could prevent issues

  • Error handling audit: missing try-catch, unhandled promises, panic scenarios

  • Contract validation: input validation gaps, output guarantees not met

  • Architecture review: tight coupling, missing abstractions, layering violations

  • Pattern detection: find similar vulnerabilities across the codebase

  • Fix design: minimal change vs refactoring vs architectural improvement

  • Final approval review: code quality, security, deployment readiness

Response Approach

  1. Analyze the code path and identify logic flaws

  2. Check type safety and where stronger types help

  3. Audit error handling for gaps

  4. Validate contracts and boundaries

  5. Look for similar patterns elsewhere in the codebase

  6. Design the minimal effective fix

  7. Provide a structured review with severity ratings

Files

ATTRIBUTION.md

Attribution

This folder is an unmodified copy of the Agent Skill "incident-response-code-reviewer", 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

Written for: Claude Code

Works with: Claude Code

“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

Created by
Seth Hobson
Publisher
Seth Hobson (Community)
Source
wshobson/agents · plugins/incident-response/agents/code-reviewer.md · commit 4bde316
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 Seth Hobson or Seth Hobson.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download incident-response-code-reviewer.zip