pragma-cli
/pragma-cli
Obsługuje CLI Pragma ADE: worktree, sesje agentów, zadania na tablicy, wątki review, transkrypty i pokazywanie kodu w edytorze.
- Autor
- pragmataW ↗
- Repozytorium
- pragma-ade ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 07.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 07.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Obsługuje CLI Pragma ADE: worktree, sesje agentów, zadania na tablicy, wątki review, transkrypty i pokazywanie kodu w edytorze.
Wyzwalacze z opisu
Oryginalny opis (EN)
Use Pragma ADE's `pragma` CLI to list and create worktrees, list and start agent sessions, manage board tasks, work through review threads (list, reply, resolve), find a session's local transcript, show code to the user in Pragma's editor or Git Changes (for that, use pragma-show), open the app you started in Pragma's browser (use pragma-browser), and publish or read step-by-step walkthroughs of code (for that, use pragma-walkthrough; to answer questions about one, pragma-walkthrough-ask). Use when working inside Pragma ADE and the user mentions worktrees, agents, the task board or review comm
Jak działa
- Commands
- Review threads
- Session transcripts
- Exit codes
Podgląd SKILL.md
---
name: pragma-cli
description: >-
Use Pragma ADE's `pragma` CLI to list and create worktrees, list and start agent sessions,
manage board tasks, work through review threads (list, reply, resolve), find a session's local transcript, show code
to the user in Pragma's editor or Git Changes (for that, use pragma-show), open the app you started in Pragma's
browser (use pragma-browser), and publish or read step-by-step walkthroughs of code (for that, use pragma-walkthrough; to answer questions about one, pragma-walkthrough-ask). Use when working
inside Pragma ADE and the user mentions worktrees, agents, the task board or review comments (to address a "Review round",
use pragma-review), or when the user asks to hand work to another agent (then use pragma-handoff) or
explicitly asks to consult another agent (then use pragma-ask).
---
# Pragma CLI
`pragma` talks to the running Pragma ADE app. Agents started by Pragma always have it on
`PATH`. If `pragma` is not found, use `"$PRAGMA_CLI"` instead; if neither works, tell the
user to enable the CLI in Pragma ADE (Settings > Command line).
Prefer `--json`: every command then prints one JSON document,
`{"ok":true,"result":…}` or `{"ok":false,"error":{"code":…,"message":…}}`.
## Commands
| Command | What it does |
|---|---|
| `pragma worktree list [--project <id>]` | Worktrees of a project (`*` marks the main one) |
| `pragma worktree create --branch <name> [--base <branch>] [--project <id>] [--path <dir>]` | New worktree |
| `pragma agent list [--worktree <id>]` | Agent sessions of a worktree |
| `pragma agent spawn --profile <id\|name> [--worktree <id>] [--prompt-file <path>]` | Start an agent |
| `pragma agent profiles` | Agent profiles (names match case-insensitively) |
| `pragma task list [--project <id>] [--column <name>]` | Board tasks |
| `pragma task create --title <t> [--description-file <path>] [--column <name>] [--priority <p>] [--labels a,b] [--project <id>]` | New task |
| `pragma task update <id> [--title <t>] [--description-file <path>] [--priority <p>] [--labels a,b]` | Edit a task |
| `pragma task move <id> --column <name>` | Move a task to another column |
| `pragma task columns [--project <id>]` | Board columns in order with their description and task count |
| `pragma task show <id>` | One task in full: column, priority, labels, worktree, description |
| `pragma comments list [--worktree <id>] [--status <open\|resolved\|all>]` | Review threads of a worktree (default open) with every reply |
| `pragma comments show <id>` | One review thread |
| `pragma comments reply <id> [--body <text>] [--file <path\|->]` | Reply to a thread (pass exactly one of `--body`, `--file`) |
| `pragma comments resolve <id> [--body <text>]` | Mark a thread resolved, optionally with a closing reply |
| `pragma comments reopen <id>` | Reopen a resolved thread |
| `pragma handoff --to <profile> --file <path\|-> [--branch <name>] [--base <branch>] [--same-worktree] [--task <id>]` | Hand off to another agent |
| `pragma session locate <id>` | Where a session's full transcript is stored (Pragma, Claude or OpenCode session id) |
| `pragma session current` | The same for your own session (`PRAGMA_SESSION_ID`) |
| `pragma ask --to <profile> [--prompt <text>] [--prompt-file <path\|->] [--timeout <seconds>]` | Ask another agent and wait for its answer (pass exactly one of `--prompt`, `--prompt-file`; only when the user asks; see pragma-ask) |
| `pragma show file <location...> [--worktree <id>] [--split]` | Open files at lines in Pragma's editor (one tab each; a location is `path[:line[-end]][:col]`; see pragma-show) |
| `pragma show diff <location> [--worktree <id>]` | Show a file's uncommitted or branch changes in Git Changes (location `path[:line]`) |
| `pragma show commit <rev> <location...> [--worktree <id>]` | Show what a commit changed in a file (parent ↔ commit) in the Git Changes tab (locations `path[:line]`) |
| `pragma browser open <url> [--worktree <id>]` | Open a URL in a new tab of Pragma's browser and show it (`localhost:5173` → http://; only after the user said yes; see pragma-browser) |
| `pragma terminal list` | The user's terminal panes of your worktree (tabs, split panes, `*` = focused; see pragma-terminal) |
| `pragma terminal read [--pane <id>] [--lines <n>]` | The last lines of a pane as plain text (default the focused pane, 100 lines, at most 2000) |
| `pragma walkthrough publish --file <path\|-> [--worktree <id>]` | Publish a step-by-step walkthrough of code to the Walkthrough tab (see pragma-walkthrough) |
| `pragma walkthrough schema` | Print the walkthrough JSON format, rules, limits and an example |
| `pragma walkthrough list [--worktree <id>]` | The worktree's walkthroughs: id, target, title, depth, steps, updated |
| `pragma walkthrough show <id> [--step <number>] [--worktree <id>]` | A walkthrough's outline, or one step (`2`, `2.1`) with its code and diffs as plain text; `<id>` may also be `current` or a commit (see pragma-walkthrough-ask) |
- `--worktree` and `--project` default to the current worktree (`PRAGMA_WORKTREE_ID`, else
the directory you are in).
- Task ids are the number (`42`) or the key (`PRA-42`); priorities are none, low, medium,
high, urgent.
- `-` as a file reads from stdin.
## Review threads
The user reviews your work in Pragma (editor, diff, browser) and presses Send. You then get a
one-line message such as `Review round 2: 3 open review threads in this worktree …`. Each
comment is a thread; the user may answer your replies in later rounds.
Use the pragma-review skill for the full procedure (what to implement, when to ask, when to
resolve). In short:
- `pragma comments list` reads the open threads; `pragma comments show <id>` reads one.
- `pragma comments resolve <id>` closes a thread you addressed (`--body` for a short note).
- `pragma comments reply <id> --body "<text>"` asks a question or answers one; leave the
thread open while you wait. `pragma comments reopen <id>` reopens a resolved thread.
## Session transcripts
Every Claude Code and OpenCode session is stored on this machine. `pragma session locate <id>`
prints the provider, the transcript `path`, its `format` and the session's `cwd`:
- Claude Code: `path` is a JSONL file (one JSON event per line); read it directly. `related`
lists subagent transcripts.
- OpenCode: `path` is its SQLite database; run the printed `read` command
(`opencode session export <id>`) to get the transcript as JSON.
The id can be a Pragma session id (`pragma agent list` shows both it and the provider session
id), a Claude session id or an OpenCode session id (`ses_…`); sessions started outside Pragma
are found too. Inside a Pragma agent, `pragma session current` needs no id. Your own provider
session id is also in the environment: Claude Code sets `CLAUDE_CODE_SESSION_ID`.
## Exit codes
- `0` ok
- `1` the app reported an error (`error.code`: invalid_argument, not_found, ambiguous,
module_unavailable, conflict, internal, timeout)
- `2` usage error (bad flags)
- `3` Pragma ADE is not running or cannot be reached; ask the user to open the app
For handoffs (giving the work to another agent), use the pragma-handoff skill. To consult
another agent when the user asks for it, use the pragma-ask skill. To work through the board's
tasks column by column, use the pragma-board skill. To address review threads, use the
pragma-review skill. To show code to the user (show me the X code), use the pragma-show skill. To offer opening a dev server you started in Pragma's browser, use the
pragma-browser skill.
To read the user's terminal output (an error they saw in their terminal), use the pragma-terminal skill.
To explain code you wrote or what a commit did step by step (walk me through), use the
pragma-walkthrough skill.
To answer a question about a walkthrough or one of its steps, use the pragma-walkthrough-ask skill.
Wersje
W bazie nie ma innych skilli o nazwie pragma-cli.
Migawka bazy z 13.11.2026 · wersja paczki d9b5d41a9670 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 95pragma-walkthrough-ask
Odpowiada na pytania o przewodnik Walkthrough w Pragma ADE, po wcześniejszym odczytaniu jego kroku w CLI. - 85pragma-show
Pokazuje kod użytkownikowi w edytorze Pragma ADE: otwiera pliki na wskazanych liniach albo pokazuje zmiany i commity zamiast wklejania w czacie. - 100sqlite
Wspiera pracę z wbudowaną bazą SQLite: tryb WAL, strojenie PRAGMA, wyszukiwanie pełnotekstowe FTS5 i współbieżność, dla aplikacji desktopowych, mobilnych i systemów wbudowanych. - 100workmux
Zarządza agentami terminalowymi, git worktree i sesjami tmux przez workmux: otwiera agentów w projekcie, sprawdza ich postęp i obsługuje równoległe przepływy agentów. - 90compact-core:compact-structure
Pomaga pisać i strukturyzować kontrakt Compact: pragmy, deklaracje stanu, typy, obwody, świadki i eksport. - 100wt
Wyjaśnia i obsługuje narzędzie wt do zarządzania worktree w gicie: tworzenie, przełączanie, listowanie i usuwanie.