df97b062755ac206b63840553e2ceb186dace238
None of the five tools could report why a command failed. mv and comment spawned without stderr set, and Bun defaults it to inherit, so the text went to the plugin host and never to the model. show, ls and init used Bun.$, whose ShellError message is only "Failed with exit code 1", and each of them interpolated just that message. The CLI explained itself every time and nothing carried the explanation. Replace all four spawn and Bun.$ blocks with one run() helper that pipes both streams and throws with stderr, and strip anyhow's "Error: " prefix so a relayed message does not read "Error adding comment: Error: ...". Verified against the real binary with a Bun.spawn shim over node's child_process, since bun is not installed here: an ambiguous show, mv and comment now each return the candidate list to the caller. The file is twenty lines shorter than the duplication it replaces. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Worklane
Worklane is a local Kanban flow for agentic software development.
Commands
| Command | Description |
|---|---|
worklane init |
Creates .worklane/ with backlog, committed, reviewing, done directories |
worklane add |
Creates a ticket in backlog with --title, --description, --acceptance, --plan, --tags, --due, --owner flags |
worklane ls |
Lists tickets, optionally filtered by --status |
worklane show <id> |
Shows ticket by UUID prefix (8+ chars) or title substring |
worklane mv <id> --status <target> [-f] |
Moves ticket between statuses. Default: forward only, one stage at a time. -f bypasses both restrictions |
worklane comment <ticket> <body> |
Adds a comment to a ticket by UUID or title |
Languages
Rust
97.8%
TypeScript
1.9%
Makefile
0.3%