codex

Delegate repo-scale coding tasks to Codex CLI for automated multi-file edits.

14|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/tae0y/python-project-template --skill codex-tae0y
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex
Source: https://github.com/tae0y/python-project-template/tree/main/.claude/skills.nouse/codex
Command: npx skills add https://github.com/tae0y/python-project-template --skill codex-tae0y

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates repo-scale coding tasks by delegating to Codex CLI, reducing manual edits and repetitive refactoring.

Core Features & Use Cases

  • Automated multi-file edits across a repository to apply changes consistently.
  • Code review assistance and scaffolding across files with verifiable outcomes.
  • Clear guardrails with explicit scope and a defined done condition to prevent scope creep.

Quick Start

Refactor all logging calls to use a centralized logger across src/ and tests/.

Frequently Asked Questions about codex

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

FAQPage Schema
How do I automate multi-file code edits across an entire repository?

Automated multi-file code edits across a repository are handled by delegating clearly scoped instructions to Codex CLI, which applies bulk changes consistently to prevent manual repetitive refactoring.

Can I use Codex CLI to bulk update type hints and formatting across my project?

Yes, Codex CLI supports bulk formatting and adding type hints across multiple files by executing deterministic patterns with a defined output file to ensure verifiable outcomes.

What is the best way to prevent scope creep during repo-scale refactoring tasks?

Preventing scope creep during repo-scale refactoring requires establishing clear guardrails with explicit scope and a defined done condition before delegating the coding task to Codex CLI.

Do I need Codex CLI access to perform automated code reviews with a verifiable done condition?

Yes, Codex CLI access is required to perform automated code reviews and scaffolding, ensuring the deterministic execution pattern produces verifiable outcomes across the repository files.

How do I refactor all logging calls to use a centralized logger across src and tests directories?

Refactoring logging calls to a centralized logger across src and tests directories is achieved by providing Codex CLI with scoped instructions to apply the automated multi-file edits consistently.