delegate-to-claude

Name: delegate-to-claude
Availability: InStock
Author: ebijun1007

Delegate GitHub issues to claude-code in a headless isolated worktree.

Updated Aug 23, 2026

Search Tags:#automation #github #orchestration #worktree #claude-code #delegate

Ready to run

npx skills add https://github.com/ebijun1007/vibe-coding --skill delegate-to-claude

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: delegate-to-claude
Source: https://github.com/ebijun1007/vibe-coding/tree/main/.codex/skills/delegate-to-claude
Command: npx skills add https://github.com/ebijun1007/vibe-coding --skill delegate-to-claude

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delegates a GitHub issue to claude-code for implementation using a headless, isolated worktree, enabling a controlled, auditable workflow.

Core Features & Use Cases

Offloads work to claude-code with a headless invocation and explicit delegation.
Maintains worktree isolation and streams stdout into the Codex pane for real-time progress.
Supports clear handoff rules, including permissions flags and user consent considerations.

Quick Start

Invoke the delegate-to-claude skill in your project to hand off an Issue to claude-code following the guidelines.

Frequently Asked Questions about delegate-to-claude

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

FAQPage Schema

How do I delegate a GitHub issue to claude-code for automated implementation?▼

To delegate a GitHub issue to claude-code, this skill uses a headless invocation within an isolated worktree, providing explicit delegation and streaming stdout back to the Codex pane for real-time progress monitoring.

What is worktree isolation in a headless claude-code workflow?▼

Worktree isolation in a headless claude-code workflow creates a controlled, auditable environment by offloading tasks to a separate git worktree, ensuring the main repository remains unaffected during automated implementation.

Can I stream stdout from claude-code back to a Codex pane in real time?▼

Yes, you can stream stdout from claude-code back to the Codex pane. This skill maintains worktree isolation while streaming output, enabling real-time progress tracking for the delegated task.

Do I need explicit permissions flags to offload work to claude-code?▼

Yes, explicit permissions flags and user consent considerations are required. The skill enforces clear handoff rules to ensure safe, controlled execution when offloading work to claude-code.

When should I use a headless worktree to orchestrate claude-code automation?▼

You should use a headless worktree to orchestrate claude-code automation when a Codex workflow needs to offload implementation tasks with explicit delegation, requiring a controlled and isolated execution environment.

What are the limitations of delegating GitHub issues to claude-code?▼

The primary limitation is that this delegation process requires explicit handoff rules and user consent. It is specifically designed for Codex workflows offloading to claude-code, not for general automated code generation.