← ClaudeAtlas

progresslisted

Use **before** starting or writing anything that will take more than about half a minute — a build, a test suite, a lint pass, a data import, a migration, a batch job, a deploy, a video encode, a long fetch loop, a script whose one job is to run one of those — so that the person who started it can watch it get there instead of guessing. One line wraps a whole command: `clawdline-progress run --label lint --typical 120 -- ./scripts/lint.sh`, and the run appears in Clawdline's bar and in a terminal status line with elapsed time and, when it has been measured, how far through it is. Triggers on "run the suite", "build it", "start the import", "kick off the deploy", "this is going to take a while", "how much longer", "is it still running", and 「跑一下測試」「開始編譯」「這要跑很久」「還在跑嗎」「大概還要多久」. Also use when adding a slow step to a script, a Makefile or a CI job. Do not use for a command that finishes at once, and not for reading or explaining a status file — this produces the progress, it does not consume it.
sainteye/clawdline · ★ 2 · Code & Development · score 68
Install: claude install-skill sainteye/clawdline
# Progress, for a run somebody is waiting on **What the reader gets.** A long command normally says nothing until it is over, and the person who started it is either sitting in front of that terminal or has no idea. This writes one small file while the run happens, and Clawdline's bar and claude-bestiary's terminal status line draw it: what is running, in which tree, since when, which phase it is in, and — when a measurement exists — how far through it is. **The person watching from a phone stops having to guess how much longer.** It is not specific to tests or builds. `label` and `phase` are free text, so a lint run, a data import, a migration and a video encode all fit the same record. ## The one line ```sh clawdline-progress run --label lint --typical 120 -- ./scripts/lint.sh ``` **Reach for this form.** The helper is the parent process, so the exit status is its own and the signals are its own: it exits on the command's own status, and a run that is killed is written down as killed. You install no traps and cannot get them wrong. - `--label` is what a person reads. Two or three words, the thing being done: `lint`, `import`, `staging deploy`. With none, the command's own file name is used. - `--typical <seconds>` is **optional, and only for a duration somebody has actually measured**. It is what turns the bar from elapsed time into a proportion. With no measurement, pass nothing: the field is then absent rather than invented, which is the whole point — to a rea