handoff-validator

Verify phase handoffs by inspecting code, running git diff HEAD, and executing tests.

15|6|Updated May 7, 2026

Search Tags:#automation #testing #validation #pipeline #handoff #git-diff

Ready to run

npx skills add https://github.com/MinhThang1009/dotclaude --skill handoff-validator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: handoff-validator
Source: https://github.com/MinhThang1009/dotclaude/tree/main/plugins/subagent-system/skills/handoff-validator
Command: npx skills add https://github.com/MinhThang1009/dotclaude --skill handoff-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill validates phase handoffs by verifying that the phase objectives are met, checks that claimed edits are real using git diff HEAD, and confirms that automated tests pass within a 120-second timeout, reducing risk in pipeline transitions.

Core Features & Use Cases

Objectives verification: compare current code state against stated phase objectives.
Edit integrity checks: count real edits vs. claimed edits across modified files using git diff HEAD.
Test execution: run a 120-second timeout test command to ensure the phase quality before moving forward.
Handoff sufficiency: determine if the phase output provides enough context for the next phase and support automated revert on failure if configured.

Quick Start

Use this skill to validate a phase handoff before advancing to the next phase.

Frequently Asked Questions about handoff-validator

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

FAQPage Schema

How do I validate phase handoffs in an automated pipeline?▼

Validating phase handoffs involves inspecting the current code state against stated phase objectives and confirming claimed edits are real by running git diff HEAD on each modified file. It tallies unverified changes to ensure outputs align with the plan.

How does git diff verification work for claimed code edits?▼

Git diff verification works by running git diff HEAD on each modified file to evaluate whether edits claimed in the handoff are real, tallying unverified changes with a safe fallback for initial commits. This confirms edit integrity.

Can I run automated tests during pipeline handoff validation?▼

Yes, you can run automated tests during pipeline handoff validation by executing a provided TEST_COMMAND. The skill runs the command within a 120-second timeout to confirm tests pass and determines whether the handoff is sufficient to proceed.

What is phase handoff validation and when do I need it?▼

Phase handoff validation is the process of verifying that phase objectives are met and automated tests pass before transitioning stages. You need it to reduce risk in pipeline transitions and ensure phase outputs provide enough context.

Do I need external dependencies to verify phase outputs against objectives?▼

You do not need external dependencies to verify phase outputs against objectives. The validation process operates independently, using git diff HEAD and a provided TEST_COMMAND to determine handoff sufficiency without extra requirements.

What happens when handoff validation fails a test execution?▼

When handoff validation fails test execution, it indicates the handoff requires a revert. The system determines the phase output is insufficient to proceed and supports automated revert on failure if configured.