status-report

Monitors herdr background coding agents, health-checks their launch flags, and reaps finished workers.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/mistakenot/skills --skill status-report-mistakenot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: status-report
Source: https://github.com/mistakenot/skills/tree/main/plugins/planning-workflow/skills/status-report
Command: npx skills add https://github.com/mistakenot/skills --skill status-report-mistakenot

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Background coding agents running under herdr can silently stall: a worker launched without permission flags reports a healthy status while being unable to run a single tool, and finished workers linger consuming full agent processes. This Skill audits every worker for a repository, reports what each is actually doing, and safely reaps the ones that are done. ## Core Features & Use Cases - Fleet status reporting: Enumerates all herdr agents filtered by repo, maps each to its task branch, and presents a table of status, health, last activity, and suggested next step. - Health verification: Inspects each worker's live process argv to detect agents running as plain shells, launched without bypass-permission flags, or misplaced in the primary checkout instead of a worktree. - Safe reaping: Removes finished workers only when their PR is merged, they are not mid-turn, and no uncommitted or unpushed work remains, removing the git worktree before closing the workspace. - Use Case: After dispatching several task workers, ask for a status report to learn that task-434 finished with PR #87 open, task-435 is mid-run, and task-436 was launched in manual approval mode and needs a reap-and-respawn. ## Quick Start Ask the agent to run a status report on the workers for this repository and reap any that are finished or unhealthy.

Frequently Asked Questions about status-report

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

FAQPage Schema
How do I check the status of background coding agents?▼

Run a status report that enumerates agents via herdr agent list filtered by repo, reads structured fields like agent_status and terminal_title_stripped, and only reads pane output for workers that are blocked or ambiguous. Results are presented as a per-worker table with next steps.

Why does my background worker show a healthy status but do nothing?▼

A worker launched without permission flags (bare claude or codex) reports a healthy done status while stalling on its first tool call in manual approval mode. Verify the live process argv with herdr pane process-info; a mis-launched worker cannot be repaired and must be reaped and respawned.

When is it safe to reap a finished worker?▼

Reap only when the worker's PR is merged or the task was abandoned, its agent_status is not working, and its worktree has no uncommitted or unpushed changes. Never reap a worker that is working, blocked, or holding an open PR.

Does closing a herdr workspace remove the git worktree?▼

No. herdr workspace close leaves the git worktree and its branch on disk. Remove the worktree first with herdr worktree remove --workspace, then close the workspace, then delete the branch once merged or abandoned.

Can I reuse a finished worker for a new task?▼

No. Workers are ephemeral: one per task, reaped on completion. Context cannot be cleared in place because /clear is cooperative and can wipe a session mid-task, and permission mode is fixed at launch, so a clean worker requires a fresh spawn.