hf.gate-stop-agents

Check for a code-changed marker before allowing agent reviews to proceed.

5|2|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/T-rav/hydraflow --skill hf-gate-stop-agents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hf.gate-stop-agents
Source: https://github.com/T-rav/hydraflow/tree/main/.codex/skills/hf.gate-stop-agents
Command: npx skills add https://github.com/T-rav/hydraflow --skill hf-gate-stop-agents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This gating skill prevents wasted review cycles by halting agent executions when no code changes are detected in the session.

Core Features & Use Cases

  • Marker-based gating: checks for a per-project code-changed marker in /tmp/claude-code-markers.
  • Exit control: exits with non-zero status to block subsequent hooks, or zero to continue when changes exist.
  • Lightweight and deterministic: runs before the Stop array to enforce gates reliably.

Quick Start

Gate agent reviews by requiring a code-changed marker; if the marker is missing, halt further hooks.

Frequently Asked Questions about hf.gate-stop-agents

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

FAQPage Schema
How do I gate CI pipelines to only run agent reviews when code changes exist?

Gate CI pipelines by checking a per-project code-changed marker in /tmp/claude-code-markers. The gate exits with a non-zero status to block subsequent hooks when the marker is missing, or exits zero to continue when changes are present.

What does a non-zero exit status do in pre-merge gate hooks?

A non-zero exit status in pre-merge gate hooks halts further agent executions and blocks downstream hooks. This prevents wasted review cycles when the required code-changed marker is not detected in the session.

How do I stop agent reviews from running on sessions with no code changes?

Stop agent reviews by enforcing a per-project marker check before the Stop array. It looks for a code-changed marker and halts execution with a non-zero status if the marker is absent.

Can I use marker-based gating in Claude pre-merge hooks?

Yes, marker-based gating works in Claude pre-merge hooks. The skill runs deterministically before the Stop array to enforce gates reliably, checking for the marker in /tmp/claude-code-markers to decide whether to proceed.

When should I use a code-changed marker check for CI automation?

Use a code-changed marker check when you need to prevent wasted review cycles in CI automation. It ensures agent reviews only proceed when actual code changes are detected in the session.

Why does my agent review continue when no code changes are detected?

Agent reviews continue when the code-changed marker is present in /tmp/claude-code-markers. If no changes exist, the gate should exit with a non-zero status to halt further hooks, meaning the marker check may not be enforced correctly.