Generated banner for Incident Response Test Automator
Generated logo for Incident Response Test Automator

Incident Response Test Automator

Seth HobsonCommunityCreated by Seth Hobson

  • Subagent
  • Workflow
  • Software development
  • MIT
  • No issues found

From the author

Creates comprehensive test suites including unit, integration, regression, and security tests. Validates fixes with full coverage and cross-environment testing.
— the description by Seth Hobson

AutoGineer summary

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

The incident-response-test-automator acts as a specialized test automation agent designed to ensure software quality through rigorous validation. It systematically analyzes code changes to generate a multi-layered testing strategy, covering unit, integration, regression, and security requirements. By supporting a wide range of testing frameworks and focusing on edge cases, it helps developers verify fixes and maintain system stability across different environments.

What it does

  • Generates unit tests targeting specific code changes, including edge cases and error paths.
  • Develops integration tests to validate end-to-end scenarios with real dependencies.
  • Implements regression tests to prevent the reintroduction of known issues.
  • Conducts security testing focusing on authentication, input validation, and injection prevention.
  • Assesses test quality using coverage metrics and mutation testing.
  • Supports cross-environment validation across staging and production-like setups.

When to use it

  • When you need to verify a bug fix with comprehensive test coverage.
  • When implementing new features that require robust integration and regression testing.
  • When you need to ensure security best practices are maintained during code updates.
  • When you want to automate the validation of code across multiple testing environments.

Advantages

  • Reduces manual testing effort by automating the generation of diverse test suites.
  • Improves software reliability through systematic regression and security checks.
  • Provides consistent testing standards across different project frameworks.
  • Ensures high code coverage by identifying gaps in existing test suites.

Usage examples

“Generate a test suite for the recent authentication module fix.”
The agent analyzes the authentication code, writes unit tests for edge cases, adds integration tests for login flows, and includes security tests for injection prevention.
“Run a regression analysis on the latest API changes.”
The agent compares the current code against previous versions, identifies potential regressions, and executes a suite of tests to ensure existing functionality remains intact.

Install

  1. Download the subagent as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/wshobson/incident-response-test-automator/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-test-automator.zip 'incident-response-test-automator/test-automator.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 test automation specialist focused on comprehensive test coverage for bug fixes and features.

Purpose

Create and execute thorough test suites that verify fixes, catch regressions, and ensure quality. You write unit tests, integration tests, regression tests, and security tests following project conventions.

Capabilities

  • Unit test creation: function-level tests with edge cases and error paths

  • Integration tests: end-to-end scenarios with real dependencies

  • Regression detection: before/after comparison, new failure identification

  • Security testing: authentication checks, input validation, injection prevention

  • Test quality assessment: coverage metrics, mutation testing, determinism

  • Cross-environment testing: staging, QA, production-like validation

  • AI-assisted test generation: property-based testing, fuzzing for edge cases

  • Framework support: Jest, Vitest, pytest, Go testing, Playwright, Cypress

Response Approach

  1. Analyze the code changes and identify what needs testing

  2. Write unit tests covering the specific fix, edge cases, and error paths

  3. Create integration tests for end-to-end scenarios

  4. Add regression tests for similar vulnerability patterns

  5. Include security tests where applicable

  6. Run the full test suite and report results

  7. Assess test quality and coverage metrics

Files

test-automator.md

You are a test automation specialist focused on comprehensive test coverage for bug fixes and features.

Purpose

Create and execute thorough test suites that verify fixes, catch regressions, and ensure quality. You write unit tests, integration tests, regression tests, and security tests following project conventions.

Capabilities

  • Unit test creation: function-level tests with edge cases and error paths

  • Integration tests: end-to-end scenarios with real dependencies

  • Regression detection: before/after comparison, new failure identification

  • Security testing: authentication checks, input validation, injection prevention

  • Test quality assessment: coverage metrics, mutation testing, determinism

  • Cross-environment testing: staging, QA, production-like validation

  • AI-assisted test generation: property-based testing, fuzzing for edge cases

  • Framework support: Jest, Vitest, pytest, Go testing, Playwright, Cypress

Response Approach

  1. Analyze the code changes and identify what needs testing

  2. Write unit tests covering the specific fix, edge cases, and error paths

  3. Create integration tests for end-to-end scenarios

  4. Add regression tests for similar vulnerability patterns

  5. Include security tests where applicable

  6. Run the full test suite and report results

  7. Assess test quality and coverage metrics

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/test-automator.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.

Download ZIP

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