gk-test

Generate regression test suites by tracing dependency blast radius across integration, component, and E2E layers.

1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/gkganesh12/gk-stack --skill gk-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gk-test
Source: https://github.com/gkganesh12/gk-stack/tree/main/skills-library/gk-test
Command: npx skills add https://github.com/gkganesh12/gk-stack --skill gk-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of incomplete test coverage and regression risks by automatically tracing the full dependency graph of code changes to ensure every affected component is verified.

Core Features & Use Cases

  • Blast-radius-aware test generation that maps direct, indirect, and contract consumers of any code change.
  • Automated test suite generation across integration, component, and E2E layers following project-specific conventions.
  • Use Case: After refactoring a core authentication module, use this skill to identify every API route, UI component, and E2E flow that depends on that module and generate the necessary tests to prevent regressions.

Quick Start

Trigger the test generation process by asking the agent to write tests for the recently modified feature files.

Frequently Asked Questions about gk-test

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

FAQPage Schema
How do I generate regression tests based on code dependency blast radius?

Blast-radius-aware test generation maps direct, indirect, and contract consumers of code changes to automatically produce regression tests across integration, component, and E2E layers.

How does blast radius analysis trace indirect dependencies for test coverage?

Blast radius analysis traces the full dependency graph of code modifications to identify every affected component, ensuring automated regression test generation covers all integration and E2E touchpoints.

How do I automatically generate integration and E2E tests after refactoring a module?

Automated test suite generation identifies API routes and UI components affected by module refactoring, then creates necessary integration, component, and E2E tests to prevent regressions.

Can I use blast-radius test generation for complex codebases with project-specific architectural patterns?

Blast-radius test generation supports complex codebases by detecting project-specific test runners and adhering to architectural testing patterns when generating comprehensive test suites.

What is the best way to verify test coverage for integration and component layers?

The best way to verify coverage is tracing the dependency blast radius of code changes to map all affected consumers, then generating verification tests across integration and component layers.

Does automated test generation work with existing project-specific test conventions?

Automated test generation adheres to project-specific conventions by detecting test runners and following established architectural testing patterns when generating regression suites.