cargo fmt --check failed in about 160 places and rustfmt was neither run nor switched off, so anyone who ran it once produced a diff that buried the change it was run alongside. It is the formatter now, and the config is what makes that affordable. The default config wanted 305 hunks and would have added 1418 lines of pure layout: its sub-widths (fn_call_width and chain_width at 60) sit far below the 100 columns this tree is written to, so 276 of those hunks were rustfmt expanding lines that already fit. `use_small_heuristics = "Max"` went the other way, 308 hunks and 796 lines removed, one-lining if/else and collapsing struct literals that were split on purpose. Coordinate descent over the stable width knobs lands at four settings and 161 hunks, 98 of them rustfmt joining calls that fit rather than breaking them. Sweeping any one of the four in either direction makes the diff bigger, which is recorded beside them so the next reader measures instead of adjusting by eye. The reformat itself is the commit after this one, so neither is mixed with the other. 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 or worklane tui [path...] |
Opens the board: four status columns, redrawn when the tree changes. Read only. Opens on backlog, committed and reviewing; d shows or hides done, whose count stays in the footer either way. Arrows or hjkl to move, enter for detail, pgup/pgdn to scroll an open ticket, whose border carries a page indicator while there is more of it than fits, / to jump to the first ticket whose id or title matches, y to copy the selected ticket's short id to the clipboard, q to quit. Each path opens the first .worklane at or above it, the working directory by default. Several paths are monitored together, as a tab per project plus an all tab that merges them, with tab and shift+tab between them |
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, --priority flags. --due takes YYYY-MM-DD and refuses anything else at parse time |
worklane ls [status] |
Lists tickets, sorted by priority then title. Optional positional status, and --priority <1-5>, --tag <tag> and --campaign <campaign>, which compose in any combination. --tag matches a whole value of the comma-separated Tags field, case sensitively, so --tag bug does not list a ticket tagged bugfix or one tagged Bug. --ids prints one ticket per line as its short id, a tab and its title, unstyled, done included, for a script or a completion |
worklane show <id> |
Shows ticket by UUID prefix (4+ chars), title substring, or filename substring |
worklane mv <id> --status <target> [-f] |
Moves ticket between statuses. Default: forward only, one stage at a time. -f bypasses both restrictions |
worklane set <ticket> |
Replaces fields with --title, --description, --acceptance, --plan, --tags, --due, --priority. At least one required. Changing the title renames the file, keeping the UUID. --clear <field> returns a field to unset instead, repeatable, taking due, tags, priority, description, acceptance or plan, and writing back exactly what add writes for a field it was never given. No title, which addresses the ticket, and no owner, which is chown's. Replacing and clearing the same field in one call is refused |
worklane append <ticket> |
Adds to a section with --description, --acceptance, --plan. At least one required. The description gains a paragraph; list items go on the end, steps numbered on from the last |
worklane relate <ticket> |
Records an edge to another ticket with --blocked-by, --regression-of or --relates-to, each repeatable. At least one required. Only the ticket named is written; show derives the other end by scanning. mv refuses to move a ticket blocked by one that is not done, unless -f |
worklane chown <user> <ticket> |
Sets the Owner field, the only command that writes it. Free text, checked against nothing. User first and ticket second, after Unix chown. worklane chown --clear <ticket> returns the field to unset, taking the ticket in the flag since there is no user to give, and not to the git user add falls back to |
worklane check <ticket> [criteria...] |
Ticks acceptance criteria, each by number as shown by show or by a substring. Several in one call, or all for every one of them. Prompts with the numbered list if none is given, or errors with it when there is no terminal |
worklane uncheck <ticket> [criteria...] |
Unticks acceptance criteria, addressed the same way |
worklane comment <ticket> <body> |
Adds a comment to a ticket by UUID or title |
worklane completions <shell> |
Prints a completion script for fish, bash, zsh, elvish or powershell. See below |
worklane install-skill [skill] |
Writes the embedded agent skills to ~/.claude/skills/<skill>/SKILL.md, which Claude Code and opencode both read. Three ship: worklane teaches the CLI, worklane-review reviews a finished ticket against the code that claims to close it, worklane-plan grooms the board as a whole, its priorities, due dates, tags and campaigns. Every document unless one is named. Leaves a modified copy alone unless --force; --print writes one to stdout instead and needs the name |
Completions
worklane completions fish > ~/.config/fish/completions/worklane.fish
Also bash, zsh, elvish and powershell, though only fish gets the dynamic half.
The structure comes from clap, so new flags appear without anyone remembering to add them. The four statuses come with it, because a status is a value enum rather than a string. On top of that, fish asks worklane for the one thing only the board knows:
worklane show <TAB> every ticket, id and title, done included
worklane mv <TAB> the same, then --status <TAB> for the four
worklane chown alice <TAB> the ticket, which is the second argument here
worklane chown --clear <TAB> the ticket, which the flag carries here
worklane relate x --blocked-by <TAB>
The tickets come from worklane ls --ids, one run per keypress, 2.5ms in release on a board of
seventy-five tickets. Since fish runs whatever worklane is on PATH, completions need the
installed binary to be current: an older one without --ids completes nothing. Re-run
cargo install --path . after pulling.
tui is the one command whose argument is a path, so it is the one place fish still offers
directories.
Exit codes
| Code | Meaning |
|---|---|
| 0 | Success |
| 1 | An error, such as no matching ticket or an ambiguous search |
| 2 | A usage mistake, such as an unknown flag, an unreal --due date, a priority out of range or a status that is not one of the four |
| 141 | Output was piped to a reader that stopped early, for example worklane ls | head -3 |
141 is 128 + 13, the shell's way of reporting death by SIGPIPE. Worklane restores
the default signal disposition so a truncated pipe is quiet, the way head and
sort are, rather than printing a panic. A script using set -o pipefail will see
141 for a case that is not a failure, so guard for it there.
Whether a truncated pipe reports 141 or 0 depends on the size of the output, not on the command. A pipe holds 64 KiB, so a listing that fits lands in the buffer whole and the writer never learns the reader left, giving 0. Only output past that gets far enough to be cut off. Either way nothing is printed to stderr.