unattended-issue-loop

Implements labeled GitHub issues and audits results in unattended cycles.

Updated Jul 13, 2026
One-click install
npx skills add https://github.com/docktermj/senzing-bootcamp-claude-plugin-development --skill unattended-issue-loop-docktermj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unattended-issue-loop
Source: https://github.com/docktermj/senzing-bootcamp-claude-plugin-development/tree/main/.claude/skills/unattended-issue-loop
Command: npx skills add https://github.com/docktermj/senzing-bootcamp-claude-plugin-development --skill unattended-issue-loop-docktermj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers of the Senzing Bootcamp Claude Plugin need a safe way to keep development moving while they are away, without an autonomous agent making judgment calls, filing issues, or shipping unreviewed decisions in their name. ## Core Features & Use Cases - Label-gated autonomy: Works only GitHub issues carrying the unattended-ok label, treating an unlabeled backlog as a deliberate no-op rather than guessing what is safe. - Alternating implement/audit loop: Drives /implement-github-issue and /production-readiness-audit in up to five cycles, stopping when an audit records no new findings. - Explicit decision contract: Encodes what an unattended run may decide (issue order, implementation approach, reverting its own work) and what it must never decide (signing off invariants, filing issues, calling submit_feedback, declining work). - Cold-readable handoff: Ends every run with a written summary of commits, deferred invariants with drafted wording, blocked issues, audit verdicts, and self-reported mistakes. - Use Case: A maintainer labels three safe issues unattended-ok, confirms push policy before leaving, and returns to find each issue implemented and committed, an audit ledger entry per cycle, and a handoff listing exactly what needs their approval. ## Quick Start Run the unattended-issue-loop skill to work through my GitHub issues labeled unattended-ok while I am away and leave me a handoff summary.

Frequently Asked Questions about unattended-issue-loop

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

FAQPage Schema
How do I run an unattended GitHub issue implementation loop?▼

Label the issues you consider safe with `unattended-ok` using the GitHub CLI, confirm push policy before leaving, then invoke the loop. It implements one labeled issue per commit, audits after each pass, and stops after five cycles or a clean audit.

What is the unattended-ok label used for in GitHub automation?▼

The `unattended-ok` label is the maintainer's explicit gate marking an issue safe for autonomous work. The loop never adds the label itself and treats any unlabeled issue as not offered, so an empty labeled backlog is a deliberate no-op.

Can an unattended agent file GitHub issues or push commits?▼

Under this contract, no. The audit records findings in the ledger marked not filed instead of calling `gh issue create`, and push policy defaults to local-only commits unless the maintainer says otherwise before leaving.

What happens when an issue cannot be implemented unattended?▼

The issue is marked blocked, never declined. The run reverts partial work, comments on the issue with the exact unblocking question, removes the `unattended-ok` label, and moves to the next labeled issue.

Why does the loop stop when the test suite cannot go green?▼

A red baseline makes failures unattributable, and weakening tests to reach green reads as false success. The run reverts to the last green commit and stops rather than continuing on a broken base.