Alien-Libgit2

 view release on metacpan or  search on metacpan

misc/agent-context/.claude/skills/kanban-issues-karr-coordination/SKILL.md  view on Meta::CPAN

bodies) a card is `k12`, never `#12` — the forge resolves `#12` against its
own issue 12. Commands take `k12` as well as `12`.

## Name yourself once

```bash
export KARR_CLAIM=$(karr agent-name)     # the checkout's directory name, e.g. "karr"
```

Claims are matched by name: `--claim` stamps it, `handoff` checks it,
`list --claimed-by` selects on it. Export `KARR_CLAIM` once per session and
leave `--claim` off: `pick`, `handoff` and `list --claimed-by` default to it,
and `move` and `edit` know a card you hold by it. `create`, `move` and `edit`
write it onto a card only when the card ends up in a `require_claim` column:
filing a card, promoting it to `todo` or adding a note leaves it free.
`archive` and `delete` ignore it — a card you hold needs `--claim NAME` there.
An explicit `--claim NAME` still wins. Agents in separate worktrees already
differ by name; several agents in the **same** directory take
`karr agent-name --unique` (`karr-8fa`).

## Read the board

misc/agent-context/.claude/skills/kanban-issues-karr-coordination/references/claims.md  view on Meta::CPAN

# Claims: pick, handoff, unlock, several agents on one board

## The claim name

Claims are matched by name: `--claim` stamps it, `handoff` and `pick` check
it, `list --claimed-by` and `log --agent` select on it. Every command taking
`--claim` (`create`, `move`, `edit`, `pick`, `handoff`, `delete`, `archive`)
and `list --claimed-by` defaults to `KARR_CLAIM`; an explicit `--claim NAME`
wins over it. `create`, `move` and `edit` are narrower: they take `KARR_CLAIM`
only when the card ends up in a `require_claim` column, so a card filed,
promoted to `todo` or annotated for others stays unclaimed. `edit --release`
never claims. `backlog` holds no claim at all: an explicit `--claim` onto a
backlog card is refused (exit 1, naming `karr move ID todo --claim NAME`), and
moving a card into backlog releases the claim it carried.
karr writes the name nowhere — it is per process, so concurrent agents never
see each other's.

misc/agent-context/.claude/skills/kanban-issues-karr-coordination/references/cross-board.md  view on Meta::CPAN

a directory from `--board NAME=PATH` or from the fleet config, matching the
repository's directory basename.

`--resolve` settles a link whose far card has reached one of the **far**
board's own terminal statuses, and lifts `blocked` when a card's last link
settles, printing the reason it lifted. A far card that does not exist settles
nothing. A board this machine cannot place is reported, not fatal.

Like `depends_on`, a cross-board link blocks nothing by itself: `pick` hands
the card over and says what it waits on. The `blocked` flag is what keeps the
card out of `pick` and out of karr-foundation's selection — the link is the
fact, `blocked` is the decision.

## How it is stored

The links ride in `tags` (`needs:BOARD#ID`, `escalated-from:BOARD#ID`), not
in a frontmatter field of their own: kanban-md marshals a card from its own
struct and would drop an unmodelled key the first time it writes, while `tags`
is modelled on both sides.



( run in 4.248 seconds using v1.01-cache-2.11-cpan-1bcd28dbaf1 )