renumber skillB
renumber is agent-read markdown (skill) from chan4lk/specclaw: Backfill ordinal number prefixes onto existing change folders — renames .specclaw/changes/<name>/ to <NNN>-<name> in creation-date order, across active and archived changes alike. Use when /specclaw:status or /specclaw:propose reports unnumbered changes, when `ls .specclaw/changes/` reads alphabetically instead of chronologically, or when the user asks to number, renumber, or reorder change folders. Shows a dry-run plan and renames nothing without explicit confirmation..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# specclaw renumber **First, run** `specclaw-ensure-init .specclaw` — idempotently creates `.specclaw/` if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name). Assign permanent `<NNN>-` prefixes to change folders that don't have them, so `ls` reads chronologically. 1. **Dry run:** `specclaw-renumber-changes .specclaw`. The tool is dry-run by default — without `--apply` it prints the plan and makes no filesystem modification whatsoever. If it prints nothing, every folder is already numbered; say so and stop. 2. Show the user the **full** `old → new` plan, every line of it, not a summary or a count. The plan is the only thing they have to judge before anything moves, and it covers both `changes/` and `changes/archive/`. 3. **Get explicit confirmation.** A "yes" to this plan and nothing weaker. Renaming is the one destructive operation in this skill; do not infer approval from a user asking a question about the plan. …
Read the whole file at its exact version.
How to install
mdr add chan4lk/specclaw/renumber@git:20260810.2b2dfc2mdr add chan4lk/specclaw/renumber@sha256:d4aab9fbbeface83Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_6vcjimrvz6ngpjdu)
1 badge views in 30 days
Versions
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2764 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
chan4lk/specclaw · 12 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6vcjimrvz6ngpjdu GET https://markdownregistry.com/api/v1/resolve?ref=chan4lk/specclaw/renumber GET https://markdownregistry.com/api/v1/blob/d4aab9fbbeface83f06c98e7fb42da3f5c83b5eec6e118b1d24b4b495faaeff4
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.