check

Verify recent work by reviewing session traces, inspecting state, and running build and test checks.

3|Updated Apr 18, 2026

Search Tags:#testing #code review #verification #build #subagent #self-check

Ready to run

npx skills add https://github.com/garochee33/DSH --skill check-garochee33

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: check
Source: https://github.com/garochee33/DSH/tree/main/agents/grok/skills/check
Command: npx skills add https://github.com/garochee33/DSH --skill check-garochee33

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you confirm that your work is correct before you finish, reducing the risk of shipping broken or incomplete changes.

Core Features & Use Cases

Subagent Verification: Spawns a verifier subagent to review diffs and judge correctness.
Build and Test Checks: Runs builds, tests, and linters to catch regressions.
Self-Verification Workflow: Repeats verification and fixes issues until the work passes or the limit is reached.
Use Case: After editing authentication logic, use this Skill to verify the change, run the relevant tests, and confirm there are no regressions.

Quick Start

Use the check skill to verify my recent changes and focus on authentication and session handling.

Frequently Asked Questions about check

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

FAQPage Schema

How do I verify code changes and run tests automatically before finishing a task?▼

To verify code changes, you can use a self-check workflow that spawns a subagent to inspect diffs, review source code, and execute build and test commands. This confirms correctness and catches regressions before completion.

How does subagent verification work for code review and build checks?▼

Subagent verification works by spawning a separate verifier agent that reviews session traces, inspects the current state, and runs build and test commands. It judges correctness independently and repeats fixes until tests pass.

Can I use automated verification for operational tasks and research, or only code changes?▼

Automated verification applies to code changes, code reviews, operational tasks, and research tasks. It requires diff inspection, source review, and execution of relevant build, test, and verification commands to confirm completion.

What is the best way to catch regressions after editing authentication logic?▼

The best way to catch regressions is running a self-verification workflow that executes builds, tests, and linters. It repeats verification and fixes issues until the work passes or the limit is reached.

Does the self-check workflow stop if the build or test verification fails?▼

The self-check workflow does not stop immediately on failure. It repeats verification and attempts to fix issues until the work passes the checks or the retry limit is reached.

When do I need to inspect diffs and source code for task confirmation?▼

You need diff inspection and source review whenever confirming completion or correctness of recent work. This applies to code changes, operational tasks, and research tasks requiring verification of build and test results.