hf-verify

Execute three-layer verification with smoke tests, code review, and mechanical gates.

51|23|Updated Apr 16, 2026

Search Tags:#quality assurance #code review #verification #HarnessFlow #transition automation

Ready to run

npx skills add https://github.com/hujianbest/harness-flow --skill hf-verify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hf-verify
Source: https://github.com/hujianbest/harness-flow/tree/main/skills/hf-verify
Command: npx skills add https://github.com/hujianbest/harness-flow --skill hf-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive verification mechanism for the HarnessFlow framework, ensuring the stability and correctness of changes in a codebase.

Core Features & Use Cases

Thorough Verification: Runs a three-layer verification process for each stage.
Runtime Smoke Testing: Validates that critical end-to-end paths function correctly.
Independent Code Review: Ensures quality by having peer reviews.
Mechanical Gate: Uses scripts to validate transitions and ensure compliance.

Quick Start

To run the verification for the feature 'feature/001-x', use the command: python3 skills/hf-workflow/scripts/hf_gate.py check --feature features/001-x --to ship

Frequently Asked Questions about hf-verify

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

FAQPage Schema

How do I automate stage transition gate checks in a code review workflow?▼

Automating stage transition gate checks requires a verification mechanism that validates compliance using scripts. This process ensures code stability by mechanically enforcing transition rules before moving changes between workflow stages.

What is the best way to verify code changes using smoke testing and peer review?▼

Verifying code changes through smoke testing and peer review is best achieved via a three-layer process. This approach validates critical end-to-end paths, ensures independent code review, and applies mechanical gates for comprehensive quality assurance.

Does HarnessFlow support automated runtime smoke testing for feature transitions?▼

HarnessFlow supports automated runtime smoke testing to validate critical end-to-end paths during feature transitions. This testing acts as a verification layer to confirm core functionality before changes proceed to the next stage.

How do I run a verification check for a specific feature transition to ship?▼

To run a verification check for a feature transition, use the gate script with the feature name and target stage. For example, executing `python3 scripts/hf_gate.py check --feature features/001-x --to ship` validates the transition.

Why do I need independent code review in my stage transition automation?▼

Independent code review is needed in stage transition automation to ensure quality through peer verification. It acts as a manual gate alongside automated smoke testing, confirming that changes meet review standards before deployment.

Can I use mechanical gates to enforce compliance for codebase changes?▼

Mechanical gates can be used to enforce compliance for codebase changes by running validation scripts. These gates ensure that all changes meet predefined criteria before transitioning, maintaining stability across the workflow.