orcakit

Reconciles Orca desktop workspaces with git worktrees by linking issues, updating statuses, and removing merged work.

1|Updated Jul 12, 2026
One-click install
npx skills add https://github.com/mimukit/skills --skill orcakit-mimukit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orcakit
Source: https://github.com/mimukit/skills/tree/main/skills/orcakit
Command: npx skills add https://github.com/mimukit/skills --skill orcakit-mimukit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? The Orca desktop app shows one workspace per git worktree, but nothing keeps that sidebar in sync with reality: worktrees sit unlinked from their issues, statuses go stale, and workspaces for already-merged work pile up indefinitely. This Skill reconciles Orca's view of your worktrees with the actual state of your git branches, issues, and pull requests. ## Core Features & Use Cases - List and audit workspaces: Render every Orca workspace as a table joined against GitHub issue and PR state, with verdicts like active, unlinked, stale, reapable, or dirty. - Link worktrees to issues: Attach issue metadata and correct workspace statuses (todo, in-progress, in-review, done) based on real tracker state, with a preview before any batch change. - Clean up merged work: Safely remove workspaces whose PRs merged and issues closed, with hard disqualifiers for dirty trees, unpushed commits, live terminals, and the current worktree. - Align worktree roots: Configure Orca's worktree base path to match the gitkit convention so future worktrees land in one location. - Use Case: After a sprint where five feature branches merged, run a cleanup to see which workspaces are reapable, confirm one batch, and reclaim the disk space while dirty worktrees are flagged for manual review. ## Quick Start Ask the agent to list my Orca workspaces and clean up the ones whose pull requests have already merged.

Frequently Asked Questions about orcakit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clean up stale Orca workspaces after PRs merge?▼

Run the clean mode, which qualifies workspaces by checking for a merged PR and closed issue via gh, then previews all candidates in one table before a single confirmation. Worktrees with uncommitted changes, unpushed commits, or live terminals are always skipped and reported with reasons.

How do I link Orca workspaces to their GitHub issues?▼

Use the link mode, which matches branches named issue-<n>-<slug> to their issues and sets the linkedIssue plus a workspace status mapped from real tracker state. It previews every planned change as one table and never overwrites an existing issue link or hand-written comment.

Does orcakit work without the Orca app installed?▼

No. If the orca CLI is missing, the skill stops immediately because there is nothing to reconcile, and worktrees remain fine without Orca. It is machine-local and optional, so no other skill in the workflow depends on it.

Can orcakit close issues or edit pull requests?▼

No. It only reads issue and PR state to judge workspace status and never writes to the tracker. When it finds a merged PR with a still-open issue, it reports the drift and routes the fix to issuekit's close command instead.

Why does Orca not show my git worktrees?▼

The repo likely has externalWorktreeVisibility set to hide, which makes git-created worktrees invisible to Orca. This is a per-repo setting in the Orca UI with no CLI flag, so you must flip it manually in the app.

When should I not use orcakit to remove a worktree?▼

Avoid it when the worktree has uncommitted changes, unpushed commits, live terminals, or is the one you are currently inside, since all of these are hard skips. Git-native worktrees are removed with plain git commands, and only Orca-created workspaces use orca worktree rm.