test

Maintain a persistent verification-and-fix loop across code changes and tests.

52|12|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/dgk-dev/dgk-gpt --skill test-dgk-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test
Source: https://github.com/dgk-dev/dgk-gpt/tree/main/skills/test
Command: npx skills add https://github.com/dgk-dev/dgk-gpt --skill test-dgk-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verification steps can get lost during iterative development; this Skill provides a persistent verification-and-fix loop that keeps validating changes, diagnosing issues, and driving fixes until the requested surface is verified or blockers emerge.

Core Features & Use Cases

  • Persistent verification loop that narrows failures and reruns checks across unit, integration, and runtime surfaces.
  • Clear target definition, automated checks, and pass/fail criteria to guide sign-off and debugging efforts.
  • Reusable workflow for bug hunts, feature verification, and regression validation across software projects.

Quick Start

Start the persistent verification loop for the current change and begin automated checks.

Frequently Asked Questions about test

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

FAQPage Schema
How do I maintain a persistent verification loop during iterative debugging?

A persistent verification loop repeatedly runs automated checks and diagnostics across code changes until the target surface is verified or blockers emerge. It defines explicit targets, pass/fail criteria, and runtime surfaces to guide iterative fixes.

What is the best way to automate bug hunts and regression validation across runtime surfaces?

Automating bug hunts requires a reusable workflow that repeatedly runs validations across unit, integration, and runtime surfaces. This narrows down failures and reruns checks until the requested surface is verified or a blocker is encountered.

How do you define pass/fail criteria for automated checks during code changes?

Pass/fail criteria for automated checks are defined by setting explicit targets and runtime surfaces before starting the verification loop. This guides sign-off and debugging efforts by evaluating whether the validation output meets the defined requirements.

Can I use this verification workflow for both feature verification and unit testing?

Yes, the verification workflow applies to feature verification, unit testing, integration checks, and regression validation. It maintains a persistent loop across these runtime surfaces to diagnose issues and drive fixes during iterative development.

When should I stop the verification and fix loop during a bug hunt?

You should stop the verification and fix loop when the requested surface is fully verified according to the pass/fail criteria, or when explicit blockers emerge that prevent further automated validation.