Alien-gettext
view release on metacpan or search on metacpan
.claude/skills/kanban-issues-karr-cli/SKILL.md view on Meta::CPAN
## Work a card
```bash
karr pick --status todo --move in-progress # most urgent free card, claimed as $KARR_CLAIM
karr move 12 in-progress # or take a specific one
karr move 12 in-progress --claim NAME # explicit claim, wins over KARR_CLAIM
karr edit 12 -a "Cause is in Foo.pm, fix pending" -t # timestamped note while working
karr edit 12 --block "needs the API change first" # stuck: say why, keep the claim â¦
karr edit 12 --block "needs k7 first" --release # ⦠or let it go for someone else
karr edit 12 --unblock
karr handoff 12 --note "Implemented, needs QA" -t # to the review column, claim refreshed
karr edit 12 --release && karr move 12 done # or close it directly
```
Columns with `require_claim` (`in-progress`, `review` on a default board)
refuse a move without a claim. A claim expires after `claim_timeout` (default
1h) and the card is free again; `pick` skips blocked cards and live claims.
Put what you learned on the card (`-a`) before handing it off â the card is
the shared memory, your session is not.
## Create a card
```bash
karr create "Title" --priority high --tags cli,bug --body 'What is wrong, how to reproduce, what done looks like'
karr create "Start now" --status in-progress # claimed as $KARR_CLAIM at creation
karr create "Ship it" --depends-on 2,3 # board-local dependency; ids must exist
karr create "New card" --json # the card as JSON: pipe the id onward
```
Bugs found on the way become cards, not silent fixes. A new card is unclaimed
unless `--status` puts it into a `require_claim` column (you are starting it)
or `--claim` says who holds it.
## Create a card on another repository's board
The board is the *target* repository's `refs/karr/*`, so a card is filed by
running `create` inside a checkout of that repository â there is no way to
name a remote and post to it directly:
```bash
karr --dir ../other-board create "Title" --body '...' # a sibling checkout you already have
git clone URL ../other-board && cd ../other-board # or clone one first, as a sibling
karr create "Title" --body '...' # create; it pulls, then pushes
```
Check the clone out as a **sibling of your current checkout â never inside its
working tree** â named for the board, where your fleet keeps its repositories.
Inside the tree it would be mixed into this repo and could be committed by
accident; a sibling stays separate, and a `needs:BOARD#ID` reference resolves
the board name to a directory by that basename (from `--board NAME=PATH` or the
fleet config) â a clone parked anywhere else is a card no one can trace back.
A fresh `git clone` carries no `refs/karr/*`, but `create` pulls the board
first (it is a mutating command), so the new id continues the remote's count â
no separate `karr sync --pull`. To record the new card as
something work *here* waits on, escalate it â
[references/cross-board.md](references/cross-board.md).
## Output flags
`--json` is taken by every board command, not by `backup`, `restore`,
`destroy`, `sync`, `set-refs`, `get-refs`. `--compact` exists on exactly nine:
`board`, `config`, `context`, `dashboard`, `list`, `log`, `metrics`, `pick`,
`show` â anywhere else it is `Unknown option: compact`, exit 2.
## When you need more
| Need | Read |
|---|---|
| Every option of `create`, `show`, `move`, `edit`, `delete`, `archive`; dependency rules | [references/cards.md](references/cards.md) |
| `list` filters and sorting, `board`, `dashboard`, `log`, `metrics`, `context --write-to` | [references/queries.md](references/queries.md) |
| `pick` ordering, `handoff` options, `unlock` for stale locks, timeouts, several agents on one board | [references/claims.md](references/claims.md) |
| A card waits on another repository: `--needs BOARD#ID`, `--escalated-from`, `karr needs --resolve` | [references/cross-board.md](references/cross-board.md) |
| `config get/set`, writable keys, the config YAML, `disable`/`enable` for karr-foundation | [references/config.md](references/config.md) |
| `sync`, fresh clones, stored card format, `materialize`/`import`, `repair`, `backup`/`restore`/`destroy`, `set-refs`/`get-refs` | [references/storage.md](references/storage.md) |
| `init`, `skill install/check/update`, `completion`, Docker | [references/setup.md](references/setup.md) |
( run in 1.394 second using v1.01-cache-2.11-cpan-99fa8243a42 )