wave-refresh

Recompute which parallel work batches can safely start against the current repository state.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/hacker-cb/claude-code-plugins --skill wave-refresh-hacker-cb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wave-refresh
Source: https://github.com/hacker-cb/claude-code-plugins/tree/main/plugins/hcb-dev/skills/wave-refresh
Command: npx skills add https://github.com/hacker-cb/claude-code-plugins --skill wave-refresh-hacker-cb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When coordinating parallel work across multiple sessions on an epic, plans go stale as code lands and issues change. This Skill recomputes what can safely start right now by diffing against the last recorded reading instead of re-surveying the entire backlog from scratch. ## Core Features & Use Cases - Differential replanning: Pins the base ref and tracker read moment, then measures only the delta since the last whole reading of the slice. - Occupied-ground detection: Cross-reads the wave ledger, the live session registry, and the files every open pull/merge request touches, surfacing disagreements as findings. - Capacity-aware layout: Rules candidates against issue currency, ground collisions, and planning axes, then reports how many batches are actually free versus how many were asked for. - Use Case: A master session coordinating an epic is asked "what else can run in parallel" after a batch lands; this Skill re-verifies affected issues, maps free ground, and hands the approved layout to the wave launcher. ## Quick Start Ask the coordinating session to refresh the wave and plan what can start in parallel, optionally naming a capacity such as "up to 3 batches".

Frequently Asked Questions about wave-refresh

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

FAQPage Schema
How do I replan parallel work batches after code lands?▼

Invoke the wave-refresh flow in the coordinating session: it pins the current base ref and tracker moment, takes the delta since the last whole reading, re-verifies only affected issues, and reports which batches are free to launch.

What is the difference between wave-refresh and backlog-survey?▼

wave-refresh is differential: it reads a delta from a recorded pin and tracker moment. backlog-survey reads every issue of a slice from scratch and is the right choice when no prior reading exists to diff from.

Does wave-refresh work with GitHub and GitLab?▼

Yes. It reads open change requests and tracker deltas through gh api for GitHub and glab api for GitLab, including pagination handling and rename detection so occupied file ground is measured completely on both forges.

When should I not use wave-refresh?▼

Do not use it when no recorded point exists to diff from — no prior refresh pin, survey pin, or ledger order pin. In that case the pass is a survey, and the skill says so and stops rather than reading the backlog under the wrong name.

Does wave-refresh launch batches or edit issues automatically?▼

No. It only reports the plan. Tracker edits execute item by item through issue-tracking on the user's word, and approved batches go to wave-dispatch, one chip per batch, launched only on explicit approval.