// End-to-end autonomous pipeline that runs auto-review-fix, then auto-pr-merge
| name | auto-submit |
| description | End-to-end autonomous pipeline that runs auto-review-fix, then auto-pr-merge |
Autonomous pipeline: review+fix code, then create PR and merge. Execute without user confirmation.
IMPORTANT: Run auto-review-fix as a sub-agent (not an inline skill) to ensure it gets its own isolated context window. This prevents instruction dilution and ensures fix phases properly spawn their own Task() sub-agents as required.
Agent(
subagent_type: "general-purpose",
description: "Run auto-review-fix",
prompt: "Run the /auto-review-fix skill. Follow ALL instructions exactly, especially: all fixes MUST be done via Task() subagents with opus-4-5. No direct edits."
)
Wait for the agent to complete. Then commit any changes:
if [ -n "$(git status --porcelain)" ]; then
git add -A && git commit -m "fix: address auto-review findings"
fi
Continue to Step 2 — do not stop here.
Use the Skill tool: skill: "auto-pr-merge"
Handles PR creation, CI polling, fix loops, and merge with --admin --squash.
Lightweight review-fix loop (2 rounds, 1 agent each), then create PR and merge
Launch, automate, and validate Electron desktop apps using playwright-cli via Chrome DevTools Protocol. Use this skill to validate UI changes in Orca, test features in the running Electron app, verify code fixes work end-to-end, or automate any Electron app (VS Code, Slack, Discord, etc.). Triggers include "validate in Electron", "test in the app", "verify the fix", "check the UI", "/electron", "automate Slack app", "control VS Code", or any task requiring interaction with a running Electron application.
Use the Orca CLI to orchestrate worktrees and live terminals through a running Orca editor. Use when an agent needs to create, inspect, update, or remove Orca worktrees; inspect repo state known to Orca; or read, send to, wait on, or stop Orca-managed terminals. Coding agents should also keep the current worktree comment updated with the latest meaningful work-in-progress checkpoint whenever useful; this is an expected default behavior, not a special trigger-only action. Triggers include "use orca cli", "manage Orca worktrees", "read Orca terminal", "reply to Claude Code in Orca", "create a worktree in Orca", "update Orca worktree comment", or any task where the agent should operate through Orca instead of talking to git worktrees and terminal processes directly.
Create PR, wait for checks, fix issues iteratively, and merge with --admin
Automated iterative code review and fix loop with parallel review agents
This skill should be used when the user asks to "optimize TypeScript performance", "speed up tsc compilation", "configure tsconfig.json", "fix type errors", "improve async patterns", or encounters TS errors (TS2322, TS2339, "is not assignable to"). Also triggers on .ts, .tsx, .d.ts file work involving type definitions, module organization, or memory management. Does NOT cover TypeScript basics, framework-specific patterns, or testing.