codex-cli

Delegate multi-step repository work to OpenAI Codex CLI via a single handoff prompt.

5|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/amirkiarafiei/subagent-cli-skills --skill codex-cli-amirkiarafiei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-cli
Source: https://github.com/amirkiarafiei/subagent-cli-skills/tree/main/skills/codex-cli
Command: npx skills add https://github.com/amirkiarafiei/subagent-cli-skills --skill codex-cli-amirkiarafiei

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It reduces the overhead of doing large, multi-step repository changes in a single chat context by delegating heavy implementation and exploration to Codex CLI while keeping the orchestration agent focused.

Core Features & Use Cases

  • Multi-step subagent delegation: Runs long-horizon repo work (edits, refactors, exploration) in an isolated Codex session using a single handoff prompt.
  • Context handoff that preserves intent: Passes the original goal, prior decisions, scope, constraints, and verification requirements so the isolated run stays aligned.
  • Verification-first outcomes: Enforces running an explicit test/lint/typecheck command before returning results, then reconciles decisions and diffs back to the main thread.
  • Use Case: When you need a feature slice that touches multiple files (implementation + docs + tests), delegate the whole plan to Codex, have it apply minimal diffs, and require the test suite to pass.

Quick Start

Ask your orchestrator agent to delegate this task to codex-cli by providing the goal, current decisions, repository scope, constraints, and the verification command you want Codex to run.

Frequently Asked Questions about codex-cli

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

FAQPage Schema
How do I delegate multi-step repository refactoring to an automated CLI?

You delegate multi-step repository refactoring to an automated CLI by passing a single comprehensive handoff prompt that preserves your goal, prior decisions, scope, constraints, and verification requirements. This triggers an isolated, non-interactive execution to apply the changes.

What is context handoff for automated code changes?

Context handoff for automated code changes is the process of passing the original goal, prior decisions, scope, constraints, and verification requirements to an isolated CLI session, ensuring long-horizon implementation runs stay aligned with the orchestration agent.

How do I run non-interactive code generation with verification testing?

You run non-interactive code generation with verification testing by executing the CLI in full-auto mode with an explicit model selection. The process enforces running a specific test, lint, or typecheck command before returning results to reconcile diffs.

Can I execute broad repo-wide edits without session bloat?

Yes, you can execute broad repo-wide edits without session bloat by using ephemeral runs. This delegates heavy implementation and exploration to an isolated session, keeping the main orchestration thread focused and preventing context window overload.

Does Codex CLI support non-interactive execution for batch edits?

Yes, Codex CLI supports non-interactive execution for batch edits through the exec command with full-auto mode. This allows you to apply minimal diffs across multiple files while requiring the test suite to pass before returning.

What are the limitations of delegating repo work to an isolated CLI session?

The limitation of delegating repo work to an isolated CLI session is that it requires a comprehensively structured handoff prompt upfront. Without passing explicit scope and verification commands, the ephemeral run cannot reconcile decisions and diffs back to the main thread effectively.