MadaraUchiha-314

MadaraUchiha-314/the-loop

Command

One self-diagnosis scan, on demand: read the-loop's own event log for harness-level failures — error-level events, terminal give-ups — debug each new one in an isolated agent one-shot, and file the findings as an issue on the-loop's own repository, labeled the-loop: self-diagnosed (issue-242).

MadaraUchiha-314/the-loop

Command

Query the structured event log — the end-to-end record of what the-loop's CLI processes decided, and why.

MadaraUchiha-314/the-loop

Command

Inspect and drive the-loop's process graph — the PDLC as an executable graph of nodes with entry and exit hooks, rather than a set of labels somebody remembers to move.

MadaraUchiha-314/the-loop

Command

Command "index" from MadaraUchiha-314/the-loop, covering commands, the control plane, daemon commands, repo-scoped commands and maintenance.

MadaraUchiha-314/the-loop

Command

Put the-loop on a machine: the CLI and the Claude Code plugin, at user or project scope.

MadaraUchiha-314/the-loop

Command

Which of the custom instruction docs your project registers actually resolve — so "is the-loop really reading my conventions?" is a question you can answer, and onMissing: error is a setting that errors.

MadaraUchiha-314/the-loop

Command

Migrate a cli-config.yaml to the current schema version. Deterministic, idempotent, and previewable.

MadaraUchiha-314/the-loop

Command

Bounce the whole system — optionally onto a new version (issue-228, decision-084).

MadaraUchiha-314/the-loop

Command

The table of Gherkin scenarios the integration tests cover — so "what is actually tested?" is a question you can answer without running anything.

MadaraUchiha-314/the-loop

Command

The work-item ↔ harness-session registry, the five execution-control commands, and the reset that forgets a work item entirely.

MadaraUchiha-314/the-loop

Command

The sessions the-loop keeps for itself — declared in the CLI config, brought up by the-loop start, and addressed by name rather than by work item.

MadaraUchiha-314/the-loop

Command

Bring the-loop up: one command that reads the CLI config and starts, detached, every service it enables (issue-228, decision-084).

MadaraUchiha-314/the-loop

Command

One report for the whole system: per service, whether the config enables it, whether it is running (and as which pid), and the poller's progress (issue-228, decision-084).

MadaraUchiha-314/the-loop

Command

Stop every running the-loop service — poller, webhook receiver, control-plane service — in reverse start order (issue-228, decision-084).

MadaraUchiha-314/the-loop

Command

Move an installed the-loop forward: the CLI and the Claude Code plugin.

MadaraUchiha-314/the-loop

Hook

Runs when a session starts on startup and resume, running an inline shell check. From MadaraUchiha-314/the-loop.

MadaraUchiha-314/the-loop

Hook

Runs when the agent finishes a response, executing the-loop-gate.py via python3. From MadaraUchiha-314/the-loop.

MadaraUchiha-314/the-loop

Cursor rule

If .the-loop/config.yaml exists in this repository, the-loop is initialized here. Operating rules: plan → execute → self/critic-review → escalate. Read .the-loop/config.yaml and follow the the-loop skill before working any ticket. If the file does not exist, the-loop is not initialized — ignore this rule (or run…

MadaraUchiha-314/the-loop

Skill Claude CodeCodex

The operating model for delivering product work items end-to-end with an agent harness. Use whenever working a ticket/issue under the-loop — to write the spec chain (requirements/design/testing-plan/tasks), execute the task DAG, verify against the testing plan, self/critic-review, escalate, present evidence, and…

MadaraUchiha-314/the-loop

Skill Claude CodeCodex

How the-loop writes for a human reader. Use when authoring or revising any artifact a person will read — requirements.md, design.md, testing-plan.md, tasks.md, a PR briefing or PR description, a decision record, a capability doc, a ticket or review comment, a README. Carries the document spine, the prefer-a-diagram…