⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

version unknown

loop-converge

levi-qiao@levi-qiao⭐ 79 stars· last commit 1mo ago· 0 open issues

Use only when the user explicitly invokes /loop-converge or names this skill. Authors a loop-converge run. Do not use unless named. Do not execute or resume generated runtime node files.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐⭐ 79 on GitHubGitHub ↗

Growing

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

loop-converge

A thin /loop-converge entry that starts a code-convergence interview, then compiles a normal loop-graph run.

English · 简体中文

/loop-converge is not a second runtime. It binds a preset pack (unused / duplicate / reuse / merge / slim; supervisor required) and follows loop-graph to generate executor, supervisor, ledger, and directives under .longgraph/<date>-converge/.

When to use it

Multi-round cleanup where "done" is checkable: tests stay green, detectors drop, net lines do not grow, no new public surface. The run sweeps the scope in rotation and discovers its own candidates each round — it ends when fresh detector passes stop yielding, not when a seeded list runs out. Skip it for a one-shot tidy. One round lands the largest safe related workset sharing a proof bar and gate; a fire cap only starts the next fire, never ends the run.

How to run it

  1. Invoke /loop-converge (Claude Code plugin: longgraph:loop-converge).
  2. Answer the short interview — scope, authority, launch — or accept the recommended A on each.
  3. A creates both nodes on Codex or Claude Code. B prints copy-ready read-and-follow prompts for another host, including Grok Build.

Authoring never executes the generated nodes.

Files

PathWhat it is
SKILL.mdEntry: fit check, bind the pack, start the interview, hand off
preset.mdAuthoring-only pack — North Star, guards, knobs, detector hints

Runtime templates live only under ../loop-graph/templates/.

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • skills/loop-converge/SKILL.md1.8 KBupstream ↗
    ---
    name: loop-converge
    description: Use only when the user explicitly invokes /loop-converge or names this skill. Authors a loop-converge run. Do not use unless named. Do not execute or resume generated runtime node files.
    disable-model-invocation: true
    ---
    
    # loop-converge — a loop-graph preset for slimming code
    
    A thin authoring entry. It binds a code-convergence pack, starts the owner
    interview, then follows [`loop-graph`](../loop-graph/SKILL.md) to compile a
    normal two-node run (executor + supervisor). It is not a third runtime node
    and it does not ship a second template set.
    
    ## Fit check
    
    - Use this when unused or duplicate code will take many verified rounds to
      remove, merge, or reuse, and an independent audit should keep the bar from
      sliding into a rewrite.
    - If the request is a one-shot tidy that fits a normal host task, say so and
      send the task directly. Do not wrap it in a graph.
    
    ## On invoke
    
    1. Inspect the workspace and the current host the same way loop-graph does.
       Never ask which client this is when context already identifies it.
    2. Read and bind [`preset.md`](preset.md). That pack **is** the North Star,
       the supervisor requirement, the method guards, the knob overrides, the
       recommended shape, and the detector hints. Do not redesign them.
    3. Start the owner interview immediately. With this pack bound, ask at most
       the three questions the pack names — **scope**, **authority**, **launch
       mode** — each as a recommended A/B (or A/B/C) choice. Do not ask for a
       North Star. Do not offer to omit the supervisor.
    4. Read and follow [`../loop-graph/SKILL.md`](../loop-graph/SKILL.md) from
       **When called from a preset skill** through generate and deliver. Compile
       only from loop-graph's [`templates/`](../loop-graph/templates/). This skill
       never executes the generated nodes.
    
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/levi-qiao-longgraph-skill-skills-loop-converge.md

// REPO STATS

79 stars
0 open issues
Last commit: 1mo ago