lemming-cli 0.4.0__tar.gz → 0.4.1__tar.gz

{lemming_cli-0.4.0 → lemming_cli-0.4.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: lemming-cli
-Version: 0.4.0
+Version: 0.4.1
 Summary: An autonomous, iterative task runner for AI coding agents.
 Project-URL: Homepage, https://github.com/owahltinez/lemming
 Project-URL: Repository, https://github.com/owahltinez/lemming

lemming_cli-0.4.1/SKILL.md

@@ -0,0 +1,103 @@
+---
+name: lemming
+description: One interface over the AI coding agent CLIs (agy, claude, codex). Delegate a single task to another agent to spare a quota or play to its strengths; run a readability, testing, or UX review over changed files, a branch, or a path; or drive a multi-task project through a roadmap that survives context limits. Use whenever work should run under a different agent than the current one, when reviewing a diff before opening a pull request, or when a job is too large for one agent run.
+license: MIT
+---
+
+# lemming
+
+One interface over several agent CLIs. You do not need to know how `agy`,
+`claude`, or `codex` spell their flags — only `lemming`.
+
+Use `exec` for one unit of work, and a roadmap for anything larger than a
+single agent run can hold.
+
+## Delegate one task
+
+```sh
+lemming exec "Fix the flaky heartbeat test in src/runner_test.py" --runner codex
+
+# Pipe a longer handoff rather than fighting shell quoting; no length limit
+cat handoff.md | lemming exec -f - --runner agy
+```
+
+The agent's closing message comes back on **stdout**, everything else on
+stderr, and the exit code is 0 only if the task completed. Read that message
+instead of hunting through logs.
+
+The task starts with an empty context and sees nothing of your conversation,
+so give it everything it needs.
+
+## Run a review
+
+With no description there is nothing for a task runner to do, so only the
+reviews run — against work that already exists.
+
+```sh
+lemming exec --review readability            # uncommitted work
+lemming exec --review testing --scope main...HEAD
+lemming exec --review all --scope src/api/
+lemming exec "Add pagination" --review all   # do the work, then gate it
+
+# Someone else's branch, in a worktree so your own tree is untouched
+git worktree add /tmp/pr-123 && (cd /tmp/pr-123 && gh pr checkout 123)
+lemming -C /tmp/pr-123 exec --review testing --scope main...HEAD
+```
+
+`--scope` takes paths, which pass through untouched, or a git revision range,
+which is resolved to the files it changed. It defaults to uncommitted work,
+and a clean tree stops the run rather than reviewing everything.
+
+Reviews **edit the workspace** — readability applies fixes and reruns checks.
+That is the point, but it means a review is not read-only.
+
+## Drive a roadmap
+
+For work that outlasts one agent run — a migration, a multi-step feature —
+break it into tasks. Each runs with a fresh context seeded only by the goal
+and recorded progress, so the project survives context limits.
+
+```sh
+lemming goal "Add offline support with a service worker and a sync queue"
+lemming add "Register the service worker and cache the app shell"
+lemming add "Queue writes in IndexedDB while offline"
+lemming run                                  # runs until the queue drains
+```
+
+Check on it, and read what an agent actually did:
+
+```sh
+lemming status              # queue, attempts, and recorded progress
+lemming status <id>         # one task in detail, including its runner command
+lemming logs                # the active task's log, or logs <id> for one task
+```
+
+Adjust it while it runs — new tasks are picked up automatically:
+
+```sh
+lemming add "Add a retry backoff to the sync queue" --index 0  # jump the queue
+lemming stop --after-current-task                             # drain, then stop
+```
+
+After each task, review hooks run automatically and a roadmap hook may revise
+the queue. `lemming hooks list` shows them; `lemming hooks disable <name>`
+turns one off for the project.
+
+## What to know before running any of it
+
+- **The agent runs unattended.** `--yolo` is the default, so it does not
+  inherit the permission prompts of whatever launched it. Treat this as
+  granting an agent unsupervised write access to the working directory.
+- **`exec` makes one attempt, no retry.** A failure is final. A roadmap task
+  retries (3 by default) with its progress carried forward.
+- **Interrupting leaves partial edits.** Nothing is restored, so there is no
+  atomicity to rely on.
+- **Concurrent runs in one checkout interleave their edits.** Give each
+  writing run its own worktree and address it with `-C`.
+- **Failures keep their state.** The directory is printed on stderr and holds
+  the run's log directly, so `cat <that dir>/*-runner.log` is the whole
+  recovery. It is retired automatically after a week.
+- **`--tasks-file` and `-C` are group options.** They go before the
+  subcommand — `lemming -C ../other exec ...`, never `exec -C ../other`.
+
+`lemming --help`, or `--help` on any subcommand, has the full flag list.

{lemming_cli-0.4.0 → lemming_cli-0.4.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "lemming-cli"
-version = "0.4.0"
+version = "0.4.1"
 description = "An autonomous, iterative task runner for AI coding agents."
 readme = "README.md"
 authors = [

lemming_cli-0.4.0/SKILL.md

@@ -1,86 +0,0 @@
----
-name: lemming
-description: Delegate a single coding task to another AI agent CLI (agy, claude, codex) through one interface, or run a code review — readability, testing, UX — over changed files, a PR branch, or a path. Use when handing work to a different agent to spare a quota or play to its strengths, or when reviewing a diff before opening a pull request. Not for driving a multi-task project; that is a roadmap.
-license: MIT
----
-
-# lemming
-
-One interface over several agent CLIs. You do not need to know how `agy`,
-`claude`, or `codex` spell their flags — only `lemming exec`.
-
-## Delegate one task
-
-```sh
-lemming exec "Fix the flaky heartbeat test in src/runner_test.py" --runner codex
-```
-
-The agent's closing message comes back on **stdout**; progress and the event
-trace go to stderr. Exit code is 0 only if the task completed. That message is
-the return value — read it instead of hunting through logs.
-
-Pipe a longer handoff rather than fighting shell quoting. There is no length
-limit, unlike a roadmap task description:
-
-```sh
-cat handoff.md | lemming exec -f - --runner agy
-```
-
-Delegate when another agent's quota, price, or strengths suit the work better
-than yours. Give the task everything it needs: it starts with an empty context
-and sees nothing of your conversation.
-
-## Run a review
-
-With no description there is nothing for a task runner to do, so only the
-reviews run — against work that already exists.
-
-```sh
-lemming exec --review readability          # uncommitted work
-lemming exec --review testing --scope main...HEAD
-lemming exec --review all --scope src/api/
-lemming exec "Add pagination" --review all # do the work, then gate it
-```
-
-`--scope` takes paths, which pass through untouched, or a git revision range,
-which is resolved to the files it changed. It defaults to uncommitted work.
-A clean tree stops the run rather than reviewing everything.
-
-Reviews **edit the workspace**: readability applies fixes and reruns checks.
-That is the point — but it means a review is not read-only.
-
-## Reviewing someone else's branch
-
-Check it out in a worktree so your own tree is untouched, and point `-C` at it:
-
-```sh
-git worktree add /tmp/pr-123 && (cd /tmp/pr-123 && gh pr checkout 123)
-lemming -C /tmp/pr-123 exec --review testing --scope main...HEAD
-```
-
-## What to know before running it
-
-- **The agent runs unattended.** `--yolo` is the default, so it does not
-  inherit the permission prompts of whatever launched it. Treat `lemming exec`
-  as granting an agent unsupervised write access to the working directory.
-- **One agent run, no retry.** A failure is final; it does not silently try
-  again. `--time-limit` caps the wall clock (default 60 minutes).
-- **Interrupting leaves partial edits.** The workspace is not restored, so
-  there is no atomicity to rely on.
-- **Failures keep their log.** The state directory path is printed on stderr;
-  read it with `lemming logs` pointed at that tasks file.
-
-## Running several at once
-
-Concurrent runs in one checkout will interleave their edits. Give each write
-task its own worktree and address it with `-C`. Read-only work parallelizes
-safely as-is.
-
-## When not to use it
-
-`exec` is for one unit of work. Anything needing more context than a single
-agent run can hold — a migration across a large codebase, a multi-step feature
-— belongs on a roadmap: `lemming add`, then `lemming run`. In particular,
-`--scope .` over a large repository *samples*; it does not cover.
-
-Run `lemming exec --help` for the full flag list.