Code from anywhere — Telegram bridge for AI coding agents (Claude Code, Codex, OpenCode, Pi, Gemini CLI, Amp). Stream progress, approve actions, and send tasks by voice from your phone.
Command Claude Code
8-step deep debugging for Untether — general sweep across fleet logs + open issues, OR targeted investigation of named GitHub issues with hypothesis + verification spec. Project-aware, fleet-aware.
Command Claude Code
This directory is the canonical source for each step of Untether's 8-step deep debugging protocol. The parent command file at ../debug.md orchestrates the steps; each file here owns the detail for one step (or one shared output).
Command Claude Code
Two templates: Debug Report (targeted mode, posted as an issue comment) and Triage Report (sweep mode, printed to stdout). Plus the Verification Spec block embedded inside the Debug Report.
Command Claude Code
This is the canonical Untether issue-class table. Pick exactly one primary class per issue (the area where the root cause lives). If behaviour crosses boundaries, note a secondary class.
Command Claude Code
This is the data-source catalogue for Untether debugging. Run the relevant sources for the classified issue type (Step 1). Don't skip — each surfaces different context.
Command Claude Code
Implement the minimal fix. Document a verification spec. Apply needs-verification. Do not close the issue.
Command Claude Code
Always research before proposing a fix. The Untether bug you're chasing is often a known upstream engine quirk, a previously-fixed regression, or a documented config gotcha.
Command Claude Code
Confirm the fix worked. Confirm no regression. Attest. Roll the fleet only after the gate is satisfied.
Command Claude Code
This is the canonical catalogue of known Untether systemic patterns. Walk this list before scoring any signal or escalating any "error" to a bug.
Command Claude Code
Escape-hatch to reconcile Untether docs OUTSIDE a PR (CHANGELOG, docs/faq/faq.md, CLAUDE.md.
Command Claude Code
Action-authority defect sweep for Untether — run the 8-step /debug engine to a verified hand-off across open actionable defect issues, one at a time, rank-ordered. Branch off dev, minimal fix, tests+lint+changelog, PR to dev, needs-verification. Runaway-capped, batch-cohesion aware. Never master/tag/release.
Command Claude Code
Capture resumable stop-state when work is genuinely paused/blocked/moving between sessions — H0 (none) / H1 (inline note) / H2 (incoming/handovers/ - .md, gitignored) / H3 (docs/handovers/ - .md, committed). Derive complete[]/decisions[]/nextaction from persisted state + evidence (git, test runs…
Command Claude Code
Execute ONE approved plan-pack phase to a verified hand-off — ground-truth the pack, compose superpowers executing-plans + test-driven-development, build in-scope only, verify (phase tests + pytest + ruff), commit to feature/ -phase-N, STOP before the PR. Refuses multi-phase. Never opens the PR (/pr-dev does) or…
Command Claude Code
Weekly, human-gated, propose-only promotion of /kaizen bullets. Parse un-struck bullets on the [kaizen] collector, score/dedupe/cluster, present approval packets; on Accept mint a propose-only artefact (pytest/doc/rule draft + GH issue) and strike the source bullet. Never auto-edits rules, hooks.json, CLAUDE.md, or…
Command Claude Code
Session-end continuous-improvement capture for Untether. Record 0-3 evidence-linked process-learnings as bullets on the permanent [kaizen] GitHub collector issue. Read-only except ONE gh issue comment. Zero captures is a valid outcome. Self-invokes at session end; propose-only downstream via /kaizen-review.
Command Claude Code
Turn an idea (incoming/ .md |.
Command Claude Code
Everyday finalise → ONE merge-ready PR to dev (→ TestPyPI on merge). Take a feature/fix/chore branch from "code+tests done" to a PR with docs reconciliation folded in as a completion criterion (CHANGELOG, FAQ touch-up, CLAUDE.md.
Command Claude Code
Release-prep for a stable version — confirm dev is green + ahead of master, bump pyproject.toml to X.Y.Z + uv lock, collapse the rc CHANGELOG sections into one dated release entry, run validaterelease.py clean, final FAQ pass, confirm the attestation marker exists, then open ONE dev→master PR and STOP. Merging that PR…
Command Claude Code
Untether's validation stage — answer "is this validated enough for its risk?" Classify the target + risk, pick the lightest sufficient depth (QA-0..QA-5), run local checks, and (opt-in) orchestrate the integration-test tiers against the allowlisted @untetherdevbot. Files capped findings, routes repair to /debug→/fix…