sweep

Run fleet-wide atmux doctor and status sweeps with triage and dry-run modes.

2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/geoyws/atmux --skill sweep-geoyws
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sweep
Source: https://github.com/geoyws/atmux/tree/main/plugins/atmux/skills/sweep
Command: npx skills add https://github.com/geoyws/atmux --skill sweep-geoyws

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It detects anomalies across all enabled atmux teams, triages the likely causes, records an auditable trail, and—when authorized—takes structural corrective actions to keep the fleet healthy.

Core Features & Use Cases

  • Fleet-wide diagnostic sweep: Runs atmux doctor and atmux status --json per enabled team to surface stalls, inconsistencies, and unhealthy states.
  • Velocity and context-pressure triage: Classifies teams by shipping progress and headroom to prioritize investigation cost and timing direction.
  • Cage-presence verification and guardrails: Uses cockpit.json cage-mode intent plus tmux socket probing to avoid false-positive escalation.
  • Action levels with audit logging: Writes actions to the complaint/audit trail before executing; supports operator-invoked one-shot or dry-run reporting.
  • Preventive fix requests and structural remediation: Can rotate leads/clear members/cycle cages, and can open atmux-source PRs when the root cause is in atmux itself.

Quick Start

Use the sweep to run a single full diagnostic and report without making any changes by giving the command: activate sweep with the verb once in dry-run mode.

Frequently Asked Questions about sweep

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

FAQPage Schema
How do I diagnose tmux fleet anomalies across multiple teams?

Diagnose tmux fleet anomalies by running a sweep that executes atmux doctor and JSON status checks per enabled team to surface stalls, inconsistencies, and unhealthy states for triage.

Can I run a dry-run diagnostic sweep without making changes to the tmux fleet?

You can run a diagnostic sweep without side effects by activating the tool with the verb once in dry-run mode to generate a full validation report and surface anomalies without applying corrective actions.

How does incident triage classify tmux team health for prioritizing investigation?

Incident triage classifies tmux team health by evaluating shipping velocity and context-pressure headroom, which helps prioritize investigation cost and timing direction for unhealthy or stalled teams.

What guardrails prevent false-positive escalations during fleet diagnostics?

Guardrails against false-positive escalations include verifying cockpit cage-mode intent and probing tmux sockets to confirm cage presence before authorizing structural corrective actions.

How does audit logging work before executing structural remediation on tmux teams?

Audit logging enforces an audit-before-action policy by writing intended actions to the complaint trail before executing structural remediation like rotating leads, clearing members, or cycling cages.

When should I request preventive fixes for atmux source code during a fleet sweep?

Request preventive fixes and open atmux-source PRs during a fleet sweep when triage identifies that the root cause of tmux fleet anomalies originates in the atmux tooling itself rather than team configuration.