cycle

Files (1)

• SKILL.md

SKILL.md (first lines)

Start (or resume) a loop-spec run from the repository. For a change across several
repositories cloned side by side in a directory that is not itself a repository, start
from that directory; when it has no `.loop-spec/workspace.json`, first write one listing
each clone the change spans: `{"repos": [{"name": "api", "path": "api"}, {"name": "web", "path": "web"}]}`.

    "${CLAUDE_SKILL_DIR}/../loop-spec/program/loop-spec" start --request "{request}"

- `{request}`: the user's request. For a spec file, pass `--request-file <path>` instead of `--request`.
- Add `--branch NAME` and `--title "..."` when the user names the branch or the PR
  title for this change.
- Add `--autonomous` if no one can answer questions during this run (a headless or
  unattended run, or arguments that start with `--autonomous`). Add `--supervised` instead
  when the arguments start with `--supervised`.
- When the request is long or holds quotes, backticks, or `$`, write it to a file and
  pass `--request-file <path>` instead of `--request`.
- Add `--kind micro` when the request is plainly a small, well-defined change, or
  `--kind debug` when it reports a failure to fix.

Then follow `${CLAUDE_SKILL_DIR}/../loop-spec/SKILL.md` until the run ends.

From aztechead/loop-spec, MIT.

More from aztechead/loop-spec