# Loopy

Discover, find, compare, audit, repair, adapt, craft, run, debrief, save, and prepare...

- Repository: https://github.com/Forward-Future/loopy (3217 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-09-11
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Forward-Future/loopy --skill loopy -g -a claude-code -y`
Codex: `npx skills add Forward-Future/loopy --skill loopy -g -a codex -y`
Cursor: `npx skills add Forward-Future/loopy --skill loopy -g -a cursor -y`
Gemini CLI: `npx skills add Forward-Future/loopy --skill loopy -g -a gemini-cli -y`

## Description

Discover, find, compare, audit, repair, adapt, craft, run, debrief, save, and prepare repeatable AI-agent loops for publication. Use when a user asks to analyze code or coding threads for recurring work, find a published loop, interview them to turn a goal into a bounded loop, review a loop for weak checks or unsafe authority, execute a loop with an evidence receipt, learn from completed runs, save or reuse a project loop, or validate and submit a loop to Loop Library.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Loopy

Help the user discover loop opportunities in existing engineering work, reuse a
published Loop Library loop when one fits, audit or repair an existing loop,
craft a new one through a focused interview, run it with evidence, learn from
the result, or prepare it for Loop Library. Treat a loop as a feedback system
with terminal states, not as permission for endless autonomy.

## Route the request

Choose the smallest useful path:

- **Discover:** Analyze a codebase, coding-thread history, or both for repeated
  work that can become a bounded loop.
- **Find:** Recommend one to three published loops for a stated problem.
- **Audit / Loop Doctor:** Diagnose an existing loop and repair only material
  weaknesses without changing its intended outcome.
- **Adapt:** Start from a published loop and replace its thresholds, tools,
  cadence, owners, or checks without weakening its feedback cycle.
- **Craft / Guided Design:** Interview the user about the outcome and what
  success means, then produce a new bounded loop.
- **Run:** Execute an identified loop within the user's authorized scope and
  return an evidence-backed run receipt.
- **Debrief:** Analyze one or more completed run receipts, diagnose what helped
  or stalled, and propose the smallest justified loop improvement.
- **Save / Reuse:** On request, save a delivered loop to the project's
  `LOOPS.md`, and reuse saved project loops when they fit a later request.
- **Publish:** Check quality and catalog overlap, prepare a publication draft,
  and submit it only with explicit approval.
- **Find, then craft:** Search first. Use the nearest published loop as a
  scaffold and ask only about the missing decisions.

Do not ask for information the user already supplied. If an audit, run,
debrief, or publication target is missing, ask the user to paste, link, or name
it. For another vague request, begin with: "What are you trying to
accomplish?"

The rest: https://github.com/Forward-Future/loopy/blob/HEAD/skills/loopy/SKILL.md