orca-finish

Certify whether an Orca-managed Git worktree is ready for manual closeout.

1|Updated Nov 11, 2012
One-click install
npx skills add https://github.com/fairchild/dotfiles --skill orca-finish-fairchild
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orca-finish
Source: https://github.com/fairchild/dotfiles/tree/main/agents/shared/first-party-skills/orca-finish
Command: npx skills add https://github.com/fairchild/dotfiles --skill orca-finish-fairchild

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Closing an Orca-managed worktree safely requires verifying that the feature branch is pushed, the PR is merged with passing checks, and no uncommitted or ignored files would be lost. This Skill performs that readiness certification without ever deleting the worktree, branch, or any Orca resources. ## Core Features & Use Cases - Read-only readiness checks: Run check mode to validate Orca identity, Git cleanliness, pushed HEAD, PR merge state, CI results, and review status without mutating anything. - Authorized certification receipts: Run prepare mode with explicit authorization to fetch remotes, validate evidence files against a repository policy adapter, and write an atomic JSON receipt outside the worktrees. - Fail-closed guardrails: Blocks on stale evidence, squash/rebase merges, credential-bearing origin URLs, remote Orca environments, and dirty or ignored files. - Use Case: Before deleting a finished Orca worktree, ask the agent to certify it; the Skill confirms the exact merge SHA contains the feature head and all required checks passed, then reports blockers or a receipt path. ## Quick Start Use $orca-finish to check whether this Orca worktree is ready to close without deleting anything.

Frequently Asked Questions about orca-finish

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

FAQPage Schema
How do I check if an Orca worktree is safe to delete?▼

Run the orca_finish.py script in check mode with the target worktree, canonical main checkout, policy adapter, and PR and completion evidence files. It returns a JSON report with ready: true or a specific blocker, and never modifies the worktree.

Does orca-finish delete the worktree or branch after certification?▼

No. This V1 is readiness-only and never stops resources, removes worktrees, or deletes branches. It warns that current public Orca removal may delete the local feature branch and leaves teardown as a separate human-controlled action.

Why does certification fail on squash or rebase merges?▼

V1 supports ancestry-preserving merges only: the feature head SHA must be an ancestor of the merge SHA, and the merge SHA must be contained by the remote default branch. Squash and rebase merges cannot be proven under this evidence contract, so they fail closed.

What evidence files are required for Orca worktree certification?▼

You need a repository policy adapter declaring required PR and completion checks, plus PR evidence and completion evidence JSON files bound to the exact repository, branch, head SHA, target path, and Orca identity. Evidence older than 15 minutes or containing raw output is rejected.

Can orca-finish run against remote Orca environments?▼

No. The script blocks when ORCA_ENVIRONMENT or ORCA_PAIRING_CODE is set, supporting only local origin-backed Git worktrees. It also rejects credential-bearing or parameterized origin URLs.