wave-harvest

Audit worker claims against git history and issue tracker status.

30|12|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/anthony-chaudhary/fak --skill wave-harvest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wave-harvest
Source: https://github.com/anthony-chaudhary/fak/tree/main/.claude/skills/wave-harvest
Command: npx skills add https://github.com/anthony-chaudhary/fak --skill wave-harvest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of drift in bulk agent operations, where workers claim tasks are complete but have not actually shipped code or closed issues, leading to a false sense of progress.

Core Features & Use Cases

  • Closure Honesty Audit: Verifies worker claims against git ancestry and issue tracker state rather than relying on log files.
  • Orphan Management: Identifies and stops spinning processes that provide no net gain, preventing resource waste.
  • Automated Re-queuing: Automatically re-queues incomplete tasks that were falsely marked as done, ensuring no work is lost between super-loop waves.

Quick Start

Run the wave-harvest skill to audit the current fleet, stop idle workers, and re-queue any incomplete leaves found in the repository.

Frequently Asked Questions about wave-harvest

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

FAQPage Schema
How do I verify if automated agent workers actually completed their git commits?

To verify automated agent workers actually completed their git commits, you can audit worker claims against git ancestry and issue tracker state, ensuring operational integrity instead of relying on potentially unreliable worker self-reporting logs.

What is the best way to stop orphaned agent processes that waste resources?

The best way to stop orphaned agent processes that waste resources is to identify and terminate non-productive spinning workers through local process management tools, preventing resource waste and removing processes that provide no net gain.

How do I re-queue incomplete tasks falsely marked as done by worker agents?

You re-queue incomplete tasks falsely marked as done by worker agents through automated reconciliation, auditing closure honesty against git ground truth and issue tracker status to ensure no work is lost between super-loop waves.

Do I need GitHub CLI to audit bulk agent task execution environments?

Yes, you need GitHub CLI to audit bulk agent task execution environments, along with git and local process management tools, to independently verify commits, check issue tracker status, and terminate non-productive workers.

Why does my bulk agent workflow show false progress when workers claim tasks are complete?

Your bulk agent workflow shows false progress because workers claim tasks are complete but have not actually shipped code or closed issues, causing drift; independent reconciliation against git ground truth resolves this operational integrity problem.