loop-it

Automate sequential GitHub issue execution with checkpointed recovery and dependency-aware ordering.

207|30|Updated May 16, 2026
One-click install
npx skills add https://github.com/smallnest/goal-workflow --skill loop-it
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loop-it
Source: https://github.com/smallnest/goal-workflow/tree/main/skills/loop-it
Command: npx skills add https://github.com/smallnest/goal-workflow --skill loop-it

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual overhead of processing open GitHub issues one by one by turning them into a controlled, recoverable implementation loop.

Core Features & Use Cases

  • Dependency-aware ordering: Reads issue bodies, detects dependencies, and processes items in a safe sequence.
  • Checkpointed execution: Persists progress to .loop-state.json so interrupted runs can resume without losing work.
  • End-to-end issue handling: Prepares branches, implements work, runs review and notes, ships changes, and cleans up branches.
  • Use case: Ideal for teams that want to batch-execute a backlog of issues while preserving traceability, failure recovery, and branch hygiene.

Quick Start

Use the loop-it skill to process all open GitHub issues in this repository with dependency-aware ordering and checkpointed resume.

Frequently Asked Questions about loop-it

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

FAQPage Schema
How do I automate GitHub issues in a batch while ensuring branch cleanup?

Automate GitHub issues by using a sequential execution loop that prepares branches, implements work, ships changes, and cleans up branches automatically. This removes manual overhead while preserving branch hygiene across multiple issues.

What is the best way to resume an interrupted GitHub issue workflow without losing progress?

Use checkpointed execution that persists progress to a .loop-state.json file. This allows interrupted runs to resume from the last checkpoint without losing work, safely handling blocked, skipped, failed, and shipped outcomes.

How does dependency-aware ordering work when processing a backlog of GitHub issues?

Dependency-aware ordering reads issue bodies to detect dependencies and processes items in a safe sequence. This ensures that prerequisite issues are resolved before dependent ones, preventing execution errors in your backlog loop.

Can I batch-execute a repository backlog if some issues have complex dependencies?

Yes, you can batch-execute a backlog with complex dependencies. The system detects dependencies from issue bodies and processes them sequentially, classifying failures and safely handling blocked or skipped items during the workflow.

What happens to the branch when a GitHub issue fails during automated execution?

When an issue fails during automated execution, the system classifies the failure and safely handles the outcome. The checkpointed state captures the failure status, allowing you to resume from that exact point without orphaning branches.

Does loop-it handle the entire issue lifecycle from branch preparation to shipping?

Yes, loop-it handles the end-to-end issue lifecycle including branch preparation, implementation, review, notes, shipping, and cleanup. This ensures traceability and branch hygiene across all processed GitHub issues in your repository.