ワンクリックで
karr
Use when managing Git-native kanban tasks or shared helper refs with the karr CLI in agent workflows.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when managing Git-native kanban tasks or shared helper refs with the karr CLI in agent workflows.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
How Langertha records Architecture Decision Records: the house docs/adr/ format, what counts as ADR-worthy in an LLM-engine framework, and the structure-first method for backfilling decisions already baked into the engine/role/value-object mesh.
Langertha's PUBLIC issue tracker — real humans' bug reports and feature requests, hosted on GitHub (github.com/Getty/langertha) and reached with the `gh` CLI. Read this whenever GitHub, `gh`, public issues, pull requests, or user bug reports come up. NOT the AI/agent work board (that is karr). HARD RULE: never touch GitHub issues — not even read — unless the user explicitly tells you to.
Moose-Klassen — Attribute, Roles vs. Inheritance, BUILD/BUILDARGS, Type-Constraints, MooseX::Singleton, make_immutable, Method-Modifier.
Langertha LLM framework — Engine creation, Raider autonomous agents, MCP tool integration, plugin system
Async Perl with IO::Async, Future, Future::AsyncAwait — lifecycle, retention, cancellation, reconnect patterns from PEVANS modules and battle-tested fixes
Commit message conventions — compact, precise, complete
| name | karr |
| description | Use when managing Git-native kanban tasks or shared helper refs with the karr CLI in agent workflows. |
Git-native kanban board for multi-agent workflows. Canonical board state lives in
refs/karr/*, not in a checked-in karr/ directory. Commands materialize a
temporary task/config view only while they run.
karr init [--name NAME] [--statuses s1,s2,s3] [--claude-skill]
Creates the board refs inside the current Git repository. With
--claude-skill, installs this skill to .claude/skills/karr/SKILL.md.
karr create "Title" [--status STATUS] [--priority PRIORITY] [--tags t1,t2] [--body TEXT]
karr create --title "Title" --assignee NAME --due 2026-03-15
karr list # all non-archived
karr list --status todo,in-progress # filter by status
karr list --priority high,critical # filter by priority
karr list --tag backend # filter by tag
karr list -s "search term" # search title/body/tags
karr list --sort priority --reverse # sort and reverse
karr list --claimed-by agent-1 # filter by claim owner
karr list --compact # one-line output (agent-friendly)
karr list --json # JSON output
karr show ID
karr move ID STATUS # move to specific status
karr move ID --next # advance one status
karr move ID --prev # go back one status
karr move ID in-progress --claim agent-1 # move and claim
karr edit ID --title "New title"
karr edit ID --priority high --add-tag urgent
karr edit ID --body "New description"
karr edit ID -a "Appended note" # append to body
karr edit ID --claim agent-1 # claim
karr edit ID --release # release claim
karr edit ID --block "Waiting on API" # mark blocked
karr edit ID --unblock # clear blocked
karr delete ID --yes # skip confirmation
karr archive ID # soft-delete (move to archived)
Idempotent — archiving an already-archived task is a no-op.
karr board
Shows tasks grouped by status.
karr pick --claim agent-1 # pick highest priority available
karr pick --claim agent-1 --status todo --move in-progress
karr pick --claim agent-1 --tags backend
Atomically finds and claims the next available task. Respects claim timeouts, blocked state, and class-of-service priority ordering (expedite > fixed-date > standard > intangible).
karr handoff ID --claim agent-1 # move to review, refresh claim
karr handoff ID --claim agent-1 --note "Done, needs QA" --timestamp
karr handoff ID --claim agent-1 --block "waiting for feedback" --release
Moves task to review, refreshes claim, optionally appends a timestamped note, blocks, or releases the claim.
karr config # show all config values
karr config get KEY # get a single value
karr config set KEY VALUE # set a writable value
karr config --json # JSON output
Writable keys: board.name, board.description, defaults.status, defaults.priority, defaults.class, claim_timeout.
karr context # print markdown summary
karr context --write-to AGENTS.md # create/update file with sentinels
karr context --sections blocked,overdue # filter sections
karr context --days 14 # lookback for recently-completed
karr context --json # JSON output
Generates a markdown summary with sections: In Progress, Blocked, Overdue, Recently Completed. Uses <!-- BEGIN kanban-md context --> / <!-- END kanban-md context --> sentinels for in-place updates.
karr skill install # install skill for detected agents
karr skill install --agent claude-code # install for specific agent
karr skill install --global # install globally (~/)
karr skill install --force # force reinstall
karr skill check # check if installed skills are current
karr skill update # update outdated skills
karr skill show # print skill content to stdout
Supported agents: claude-code, codex, cursor.
For Docker-wrapped usage, prefer the raudssus/karr:latest alias that mounts
the current project at /work and uses /home/karr as HOME, so the image
can drop privileges to the owner of the mounted workspace without breaking
access to Git config or agent skill directories.
karr sync
karr sync --pull
karr sync --push
Use this when you want explicit control over board ref exchange with the remote instead of relying only on the implicit pull/push behavior of mutating commands.
karr backup > karr-backup.yml
karr restore --yes < karr-backup.yml
restore is destructive and replaces the entire refs/karr/* namespace.
karr destroy --yes
Deletes the entire refs/karr/* namespace from the repository and prunes the
remote board state too when a remote is configured. Prefer taking a
karr backup first.
karr set-refs superpowers/spec/1234.md draft ready
karr get-refs superpowers/spec/1234.md
Stores and retrieves helper payloads in Git refs outside protected namespaces
such as refs/karr/*, branches, and tags. Use this for shared planning blobs,
agent scratch data, or similar workflow artifacts that should sync through Git
without becoming task cards.
karr log # last 20 entries
karr log --agent swift-fox # filter by agent
karr log --task 5 # filter by task
karr log --last 50 --json # more entries, JSON
karr agentname # generate random two-word name
karr pick --claim $(karr agentname) --move in-progress
---
id: 1
title: Set up CI pipeline
status: backlog
priority: high
class: standard
created: 2026-03-12T10:00:00Z
updated: 2026-03-12T10:00:00Z
tags:
- devops
---
Optional body with more detail.
Tasks are stored under refs/karr/tasks/*/data. During command execution karr
materializes the same Markdown shape into a temporary task directory, so this
format still matters when reading or generating tasks programmatically.
version: 1
board:
name: My Project
statuses:
- backlog
- todo
- name: in-progress
require_claim: true
- name: review
require_claim: true
- done
- archived
priorities: [low, medium, high, critical]
claim_timeout: 1h
defaults:
status: backlog
priority: medium
class: standard
That YAML lives in refs/karr/config as sparse overrides. The next numeric id
is kept separately in refs/karr/meta/next-id.
karr initkarr create "Title" --priority highkarr board or karr listkarr pick --claim NAME --move in-progresskarr handoff ID --claim NAME --note "reason"karr edit ID --release && karr move ID donekarr edit ID --block "reason"karr show IDkarr archive IDkarr context --write-to AGENTS.mdkarr config / karr config set KEY VALUEkarr skill installkarr backup / karr restore --yeskarr set-refs / karr get-refskarr destroy --yes# 1. Generate agent name and pick task
NAME=$(karr agentname)
karr pick --claim $NAME --status todo --move in-progress
# 2. Work on task...
# 3. Hand off for review
karr handoff ID --claim $NAME --note "Implementation complete" --timestamp
# 4. Or: release and mark done directly
karr edit ID --release
karr move ID done
Claims expire after the configured timeout (default: 1h). Statuses with require_claim: true enforce that moves include --claim.
Perl remains the primary local installation path, but a Docker alias around
raudssus/karr:latest or raudssus/karr:user works with the same commands when
another repository vendors karr instead of installing it locally.
# 1. Publish a shared planning blob
karr set-refs superpowers/spec/1234.md initial draft ready for review
# 2. Read it back elsewhere
karr get-refs superpowers/spec/1234.md
Use helper refs for coordination data that should travel with Git but should not affect the board state itself.