Agent skill · Code Review & Quality

loop-it

Automated issue loop with checkpoint/resume: fetch open GitHub issues → dependency-aware topological sort → implement each issue end-to-end → review with /review-it → document with /note-it → ship with /ship-it → repeat. Persists state to .loop-state.json for crash recovery. Triggers on: loop-it, loop issues, auto implement, 批量实现, 循环实现, 实现所有issue, 恢复循环, resume loop.

smallnestgithub.com/smallnestGitHub ↗
claude-codecodexread-onlyMIT
Install
npx skills add smallnest/goal-workflow --skill loop-it --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 15 KB
Bundled scripts: none
Allowed tools: -Bash(gh:*)-Bash(git:*)-Bash(cat:*)
Path: skills/loop-it/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 199
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# loop-it — 带检查点恢复的自动化 Issue 实现循环 Fetch all open GitHub issues, resolve dependency order, implement each through the full pipeline (内联实现 → `/review-it` → `/note-it` → `/ship-it`), persist progress to state file, and resume from checkpoint on crash. > **⚠️ 关键前提:实现步骤由 agent 内联自主完成,不依赖任何外部 `/goal` 命令。** > 本环境中不存在可调用的 `goal` 命令或 skill。因此「实现 issue」这一步**必须由 agent 内联完成**:直接读取该 issue 的标题与正文(含其引用的 PRD/SPEC 与验收条件),自主完成"理解需求 → 写/改代码 → 跑测试与 lint → 满足全部验收条件"的闭环,持续工作直到该 issue 的验收条件全部满足且测试/构建通过。**不要**尝试用 Skill 工具调用 `goal`(会报 `goal is a UI command, not a skill`),也**不要**因为找不到 `/goal` 而中止循环。`/review-it`、`/note-it`、`/ship-it` 仍是真实 skill,经 Skill 工具调用。 --- ## Overview ``` 前置检查 → 读取状态文件 → Fetch Issues → 构建依赖图 → 拓扑排序 | ┌───────────────────────────────────────────────────────────┘ | v ┌──────────────── 单 Issue 循环 ────────────────┐ | | | 从检查点恢复?—— 跳过已完成/失败的 | | | | 分支准备 (checkout main, pull, create branch) | | | | | Skip/Blocked? ── 是 → 标记 skipped/blocked, 写检查点 | | | | | 否 | | | | | 内联实现 → 出错?→ 分类 → 恢复 → 重试 | | | | | | | 失败 → 检查点, 下一个 | | | | | /review-it → 有问题?→ 修复 → 重跑 review | | | | | /note-it (捕获实现笔记, best-effort) | | | | | /ship-it → 出错?→ 分类 → 恢复 | | | | | 分支清理 (checkout main, pull, delete branch) | |

What's inside
Steps it walks through
  1. Overview
  2. 前置检查
  3. Check 1: gh CLI 认证
  4. Check 2: Git 仓库
  5. Check 3: Git 工作树清洁度
  6. Check 4: 在默认分支上
  7. Check 5: 远程可达
  8. Check 6: 状态文件存在?
  9. 状态文件
  10. 位置
  11. 格式
  12. 状态值
  13. 写入规则
  14. Step 1: Fetch Issues & Build Dependency Graph
Commands it runs
gh auth status
git rev-parse --is-inside-work-tree
git status --porcelain
git branch --show-current
git ls-remote --heads origin
cat .loop-state.json
gh issue list --state open --json number,title,labels,body --limit 100
git checkout main
git pull
git checkout -b feat/issue-{N}-{short-desc}
More from goal-workflow
All skills →
About this skill
What does the loop-it skill do?

Automated issue loop with checkpoint/resume: fetch open GitHub issues → dependency-aware topological sort → implement each issue end-to-end → review with /review-it → document with /note-it → ship with /ship-it → repeat. Persists state to .loop-state.json for crash recovery. Triggers on: loop-it, loop issues, auto implement, 批量实现, 循环实现, 实现所有issue, 恢复循环, resume loop.

How do I install it?

Run `npx skills add smallnest/goal-workflow --skill loop-it --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From smallnest/goal-workflow, a repository with 199 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going