tilldone

Run a command per package until phase states converge or a fixed count.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/EndUser123/cc-skills-utils --skill tilldone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tilldone
Source: https://github.com/EndUser123/cc-skills-utils/tree/main/skills/tilldone
Command: npx skills add https://github.com/EndUser123/cc-skills-utils --skill tilldone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running commands across many packages in a directory can be tedious and error-prone. Tilldone automates per-package execution until convergence or a fixed number of passes, reducing manual work and ensuring consistent outcomes.

Core Features & Use Cases

  • Till-done convergence: repeatedly runs the target command for each package until the phase states in references/changelog.md stop changing.
  • Fixed-count mode: executes a user-specified number of passes per package for deterministic results.
  • Per-package reporting: provides a stability report per package and a final summary.

Quick Start

Invoke /tilldone on a target directory to run a command per package until phase states converge or a fixed count is reached.

Frequently Asked Questions about tilldone

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

FAQPage Schema
How do I automate running commands across multiple packages until they converge?

Batch convergence for per-package commands is achieved by repeatedly running a specified command across packages in a target directory until phase states in references/changelog.md stop changing.

What is per-package command convergence in a batch directory?

Per-package command convergence is the process of reading references/changelog.md before and after each command run to determine if package phase states have stabilized, stopping execution once changes cease.

How do I run a fixed number of command passes over a directory of packages?

Running a fixed number of command passes over a directory of packages is supported through a fixed-count mode that executes a user-specified number of iterations per package for deterministic results.

Can I get a stability report for each package after batch command execution?

Getting a stability report for each package after batch command execution is supported, providing per-package convergence results alongside a final summary of all outcomes via the Skill tool.

Do I need a references/changelog.md file in each package directory for convergence detection?

A references/changelog.md file in each package directory is required for convergence detection, as the tool reads this file before and after each run to monitor changes in phase states.