Przejdź do treści
Biblioteka skilli
Programowanie · Integracja z narzędziem

orca-cli-local

/orca-cli-local

Stosuje lokalne wnioski przy każdym użyciu CLI Orca (orca-ide, orca-dev), także przed utworzeniem worktree gałęzi lub prośbą o opinię przed commitem w Orca.

Repozytorium
ai-config ↗
Licencja
GPL-3.0
Ostatnia zmiana repozytorium
08.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
4
Przestarzałość

Brak sygnałów. Repozytorium zmienione 08.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

GPL-3.0, otwarta.

Co robi i kiedy

Stosuje lokalne wnioski przy każdym użyciu CLI Orca (orca-ide, orca-dev), także przed utworzeniem worktree gałęzi lub prośbą o opinię przed commitem w Orca.

Oryginalny opis (EN)

Applies local lessons to every use of the Orca CLI (orca-ide, orca-dev). Use alongside the upstream orca-cli skill whenever the Orca CLI is needed, including before creating a branch worktree or asking the user for feedback on a change before committing while running inside Orca.

Jak działa

  1. "Start this in a separate worktree" means an agent runs there
  2. Never trust the repo's configured base ref
  3. Every new worktree gets its own agent
  4. Name every agent you start
  5. Handles go stale quickly
  6. Talking to agents you started
  7. Offer Orca's diff view for review
  8. Workaround: worker tabs titled worker-task<id>
  9. Workaround: Orca narrows fork remotes, hiding fork PRs
  10. Read the screen before every send
Sekcje z nagłówków SKILL.md, w oryginale · 197 linii, 1 436 słów
Podgląd SKILL.md
---
name: orca-cli-local
description: Applies local lessons to every use of the Orca CLI (orca-ide, orca-dev). Use alongside the upstream orca-cli skill whenever the Orca CLI is needed, including before creating a branch worktree or asking the user for feedback on a change before committing while running inside Orca.
---

# Local orca-cli guidance

Load the upstream `orca-cli` skill for the command surface, then apply these
rules to every Orca CLI command. Each one exists because the upstream
defaults or an agent's assumptions produced the wrong result: on 2026-09-17
(tacticalvote), a worktree with an idle shell instead of a working agent,
branched from a stale base; later, a coordinator that denied having a
message channel, and prompts typed into agents' dialogs.

## "Start this in a separate worktree" means an agent runs there

When the user asks for work to be started, done, or handed off in a new
worktree, they expect to watch an agent working in that worktree's terminal.
Doing the work from the current session while the new terminal sits idle is
the failure to avoid.

- Pass `--agent <id> --prompt "<full brief>"` in the same `worktree create`
  call. Default to `claude` unless the user names another agent.
- The brief must be self-contained: the original request verbatim, the PR
  target branch, and any repo constraints the current session already
  learned (test commands, hosting, files to look at). If the user tests
  through a `working` mixdown branch in that repo, say so and tell the
  worker to load `git-branch-management` before its first commit.
- After create, `terminal read` the returned agent handle and confirm the
  brief is visible before reporting the handoff as started.
- Only work in the new checkout from the current session if the user
  explicitly says so.

## Never trust the repo's configured base ref

Upstream says to omit `--base-branch` for independent work so Orca uses the
repo default base. That default is stored Orca config and drifts: for
tacticalvote it still pointed at `origin/locals-2025`, 211 commits behind
`origin/main`, the branch PRs actually target.

- Determine the PR target first (`gh repo view --json defaultBranchRef`,
  recent `gh pr list --json baseRefName`, or CLAUDE.md), then pass it with
  `--base-branch origin/<target>` explicitly.
- Read `baseRef` and `head` from the create result and check `head` equals
  `git rev-parse origin/<target>`. If not, remove the worktree
  (`worktree rm --force`, safe only while it has no changes) and recreate;
  do not rebase or `reset --hard` inside it.
- When the configured base is stale, fix it once with
  `repo set-base-ref --ref origin/<target>` and tell the user.

## Every new worktree gets its own agent

When running inside Orca (`ORCA_PANE_KEY` is set) in a repository with an
`orca.yaml`, or registered in Orca, create every new worktree with
`worktree create`, including one for your own next change. Outside Orca the
CLI cannot create one; follow `git-branch-management` instead.
`git worktree add` and `wt switch --create` skip Orca's setup, leaving no
dependencies or env files. Pass `--no-parent`, `--base-branch
origin/<target>` (see above), and `--setup run` unless the repository's
setup policy already runs it.

A new worktree exists so that a new agent can work in it, even when the
user only asked for the change and never mentioned a worktree, and even
when you are already an agent in another worktree. Pass `--agent` and a
self-contained `--prompt` in the same `worktree create` call, following the
handoff rules above, and do not edit, build or test in that worktree from
the current session. If you need its result, start a supervised worker
instead (see "Talking to agents you started"). The agent's start waits for
setup only when the repository sets `setupAgentStartupPolicy:
wait-for-setup`; otherwise tell it in the brief to check that setup has
finished first.

Work in the new worktree yourself only when the user explicitly says so.
Then, before editing, `terminal list --worktree <selector>` and `terminal
read` the setup terminal to confirm setup finished without errors.

## Name every agent you start

Give each agent session you start a 3–6-word name for its task, so it is
recognisable in the agent's session picker and in its Orca tab, which shows
the agent's terminal title.

- With `terminal create --command`, put the name on the agent's command
  line: `claude --name "<name>" …` or `pi --name "<name>" …`. Codex has no
  launch-time name flag.
- Set the initial name with the agent's `--name` flag. Omit
  `terminal create --title` when the tab should follow later session
  renames; that flag pins a separate Orca label. Use it only when a fixed
  tab label is intended.
- `worktree create --agent` cannot pass agent arguments until
  [`stablyai/orca#25067`][orca-25067] lands, so those sessions keep the
  agent's automatic title. Don't abandon `--agent` just to name one.

[orca-25067]: https://github.com/stablyai/orca/issues/25067

## Handles go stale quickly

A `terminal wait` on the create-returned handle can report
`terminal_handle_stale` within a minute while the agent is in fact running.
Re-list terminals for the worktree and continue with the replacement handle;
do not treat the stale error as a failed handoff.

## Talking to agents you started

Orca has inter-agent messaging (`orchestration --help`). Never tell the user
that typing into a terminal is the only way to reach an agent.

Messaging is pull-only for plain handoff agents: Orca's hooks inject no
mail, so a recipient sees messages only when it runs
`orca-ide orchestration check`. Set the channel up in the initial
`--prompt` brief:

- the coordinator's handle (`$ORCA_TERMINAL_HANDLE`);
- "run `orca-ide orchestration check --terminal "$ORCA_TERMINAL_HANDLE"`
  at each checkpoint"; and
- "report with `orca-ide orchestration send --to <coordinator handle>
  --type status|question|escalation`".

Don't ask a plain handoff agent for `worker_done`; without a Dispatch it is
rejected ("worker_done requires taskId"). When you want reports or
supervision from the start, use supervised workers instead
(`orchestration run-create`, then `worker-start`; see the `orchestration`
skill).

When several agents work related beads in parallel, give each one's brief the
others' terminal handles and bead IDs, and tell it to:

- run `orca-ide orchestration send --to <handle>` whenever a finding unblocks
  or changes a sibling's bead, as well as commenting on that bead
  (`beads-best-practices`); and
- run `orca-ide orchestration check --terminal "$ORCA_TERMINAL_HANDLE"` while
  waiting on another bead, since messages are pull-only.

Supervised siblings in one Run can use the Run's group addresses instead
(`orchestration` reference `messaging-and-gates.md`).

## Offer Orca's diff view for review

When running inside Orca and you need the user's feedback on a change
before committing, never put it in a Markdown file for them to review.
Leave the edit uncommitted, and offer, as one option in your question, to
open each changed file in its own tab with `file diff <path> --worktree
<selector>`. Open the tabs only if the user picks that option. Showing the
change in chat through the harness's own diff display is also fine.

A diff tab shows every uncommitted change in that file, not only yours. If
the file also has hunks you didn't write, say so when you offer the tab, and
say which hunks are yours.

## Workaround: worker tabs titled `worker-task_<id>`

Temporary, until [`stablyai/orca#21917`][orca-21917] is fixed (seen in
1.4.219). `orchestration worker-start` stores `worker-<task id>` as the
custom title of each worker terminal it creates. A custom title outranks
Orca's task-derived title and the agent's own title, so the tab stays
unreadable whatever `--task-title` says.

Pass a readable `--task-title` to `worker-start`. Then, if it created a
terminal (no `--terminal`), clear the placeholder so the tab shows that
task title:

```sh
orca-ide terminal rename --terminal <worker handle>
```

The handle is `worker.agentTerminalHandle` in `orchestration worker-show
--dispatch <id> --json`. Omitting `--title` only removes the placeholder;
setting one would pin it over every later title. Workers without a terminal
need nothing.

[orca-21917]: https://github.com/stablyai/orca/issues/21917

## Workaround: Orca narrows fork remotes, hiding fork PRs

Temporary, until [`stablyai/orca#25703`][orca-25703] and
[`#12956`][orca-12956] are fixed (seen in 1.4.219). When a worktree's PR
comes from a fork, Orca reuses any remote with the fork's URL, including one
the user added, and replaces its `+refs/heads/*` fetch refspec with one for
that worktree's branch only. Other branches pushed to that remote then get no
tracking ref, and Orca shows no PR for them.

After pushing a worktree's branch to a remote other than `origin`, run
`git rev-parse --abbrev-ref @{u}`. If it fails with "not stored as a
remote-tracking branch", tell the user, and ask before running
`git config --add remote.<name>.fetch '+refs/heads/*:refs/remotes/<name>/*'`.
Leave Orca's per-branch lines in place. Orca still strips the wide line again
when a new fork-PR worktree on another branch is set up.

[orca-25703]: https://github.com/stablyai/orca/issues/25703
[orca-12956]: https://github.com/stablyai/orca/issues/12956

## Read the screen before every send

Before any `terminal send` to an agent, `terminal read` it. Send only if it
is idle at its normal input prompt: no dialog, menu, questionnaire,
permission prompt, running turn, or startup screen. `tui-idle` alone is not
enough; typed text and Enter can answer a dialog and change its settings.

Otherwise skip that terminal and report it to the user. After sending,
`terminal read` again to confirm the text arrived as a prompt.

Wersje

W bazie nie ma innych skilli o nazwie orca-cli-local.

Migawka bazy z 13.11.2026 · wersja paczki e404f6bd1cf1 (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

  • 100orca-cli
    Obsługuje przez CLI orca drzewa robocze, konteksty folderów, terminale, repozytoria, automatyzacje, artefakty, współdzielenie skilli i wbudowaną przeglądarkę Orca, w tym uruchamianie agentów w osobnych worktree.
  • 100orca-cli
    Obsługuje polecenia CLI Orca do zarządzania worktree, terminalami, repozytoriami, automatyzacjami i wbudowaną przeglądarką oraz do przekazywania pracy innemu agentowi.
  • 100orca-setup
    Konfiguruje repozytorium dla Orca tak, by każdy nowy worktree był gotowy do pracy: kopiuje ignorowane pliki env z głównego checkoutu i uruchamia pnpm install; obejmuje orca.yaml i hooki setup oraz archive.
  • 100orca
    Uruchamia przepływ Orca, czyli autonomiczny wieloagentowy proces plan, kod, przegląd w CLI bez interfejsu, któremu zleca się dobrze zdefiniowane zadanie implementacyjne zamiast robić je samodzielnie.
  • 100orca
    Obsługuje aplikację Orca, która uruchamia kilku agentów kodujących, takich jak Claude Code i Codex, równolegle w osobnych git worktree, na przykład do porównania wyników na tym samym zadaniu.
  • 100orca-emulator
    Steruje strumieniem emulatora lub symulatora iOS z poziomu Orca przez CLI orca: dotknięcia, gesty, pisanie, przyciski sprzętowe, wstrzykiwanie obrazu z kamery, uprawnienia i drzewo dostępności z podglądem na żywo.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.