#Codex
Explore public prompts for Codex. Narrow the topic by medium or change the order.
Showing 1–18 of 18 · Page 1 / 1
AGENTS.md Starter Kit: Minimal and Advanced Templates for Codex and Any Agent
Two AGENTS.md templates drawn from Ischca/awesome-agents-md (CC0): "minimal" is a five-line checklist you can run with right away, and "advanced" covers five sections — environment, testing, conventions, safety, and example tasks. They let an AI coding agent know the rules the moment it enters your project.
Codex config.toml in Practice: Approval Modes × Sandbox Isolation × Profiles
A ready-to-paste ~/.codex/config.toml template that sets up OpenAI Codex CLI's approval policy, sandbox isolation, reasoning effort, and multiple profiles in one go — balancing automation efficiency with safety boundaries.
Codex Skills Mode: Installing Skill Packs and an Autonomous Implementation Loop (cc-sdd)
Uses cc-sdd's --codex-skills install to load reusable skills (SKILL.md) into Codex CLI on demand, and replicates its /kiro-impl autonomous execution loop — a fresh implementer per task, an independent reviewer, and automatic root-cause debugging on failure — so Codex advances steadily through a task list one task at a time.
Codex exec Non-Interactive Mode: Wiring Codex Into a CI Automation Pipeline
Uses codex exec's non-interactive execution plus a restricted sandbox to plug Codex CLI into CI / scripted workflows for unattended tasks like lint fixes, batch refactors, and auto-repair, guarding the safety boundary with approval_policy=never paired with a workspace-write sandbox.
OpenAI Codex's AGENTS.md: Rules for AI Written by a Real Large Project
A breakdown of the AGENTS.md actually in use in OpenAI's official codex repository — see how a project with millions of lines of code writes team conventions like formatting, testing, commits, module size limits, and API naming into an instruction file that an AI agent can understand and follow, plus a Traditional Chinese adaptation template you can apply directly to your own project.
The AGENTS.md Starter Template: A Minimal File Any AI Agent Can Understand
The AGENTS.md file from the official agents.md standard project itself, demonstrating what a 'minimal but complete' agent rules file looks like — telling AI to use the dev server instead of building during development, restart after dependency changes, and which commands run lint/test/build — with a directly reusable template.
Codex Iterative Repair Loop: Review → Repair → Validate Until Broken Code or Docs Pass
An OpenAI Cookbook Codex example that turns 'fixing bugs or outdated examples' into a self-iterating closed loop: first review and list the problems, then make a targeted fix on a copy, then run validation and score it, and if it doesn't pass, feed the remaining issues back in for another round — until everything's green or a cap is hit. Includes three ready-to-use prompt templates.
VoltAgent Codex Subagent Directory: Installing Specialist Agents via TOML in ~/.codex/agents
Uses VoltAgent/awesome-codex-subagents (166+ subagents, 13 categories, MIT license) as a Codex-equivalent curated directory, teaching you to define subagents in .toml format under ~/.codex/agents/ and invoke Codex subagents explicitly.
Advanced Codex CLI Playbook: Layered AGENTS.md + config.toml + Research-to-Ship Workflow
Upgrades OpenAI Codex CLI from 'vibe coding' into a controllable engineering agent: layered AGENTS.md, approval and sandbox settings in .codex/config.toml, and Starlark command gating, paired with a five-stage Research → Plan → Execute → Review → Ship workflow.
Codex AGENTS.md Generator: Turn Project Rules into an Instruction File Codex Understands
Have the agent interview you about your project, then produce a structured, no-fluff AGENTS.md that spells out build/test commands, code style, commit conventions, and off-limits areas in one shot — auto-loaded every time work starts.
Codex's Four-Gate Kickoff: Define the Task → Review the Plan → Check the Diff → Nothing Counts as Done Without Verification
Turns a vague requirement into a full Codex workflow: first force it to nail down a 'definition of done,' use plan mode to produce a plan for your approval, then implement in small steps, run its own tests, and finally produce a reviewable diff with verification evidence.
Codex Wrap-Up Officer: Turn Finished Changes into a Semantic Commit + a PR That Passes Review
Once your code changes are done, have Codex read the staged diff, produce a Conventional Commits message, and write a PR description covering background, what changed, why, how it was verified, and risks — without bundling in unrelated changes, exaggerating, or fabricating tests.
Codex Rigorous Diff Reviewer: Correctness, Simplification, and Security in Three Tracks
Has Codex do a disciplined code review of your git diff across three tracks (correctness bugs / simplification-and-reuse / security), listing each finding with a confidence level and a pastable fix, and explicitly instructed to say so when nothing's wrong instead of manufacturing complaints.
Codex Bug-Fix Closed Loop: Reproduce First, Fix Second, With Rerunnable Verification
Forces Codex through a closed loop — write a failing test that reproduces the bug, find the root cause, make the minimal fix, watch that same test go from red to green, then run the full test suite to confirm no regressions — eliminating both 'fixed it without verifying' and 'changed a bunch of unrelated stuff along the way.'
Codex Characterization Tests for Legacy Code: Lock In Current Behavior, Target Edge Cases, Zero Behavior Changes
Has Codex write characterization tests for untested legacy code: it first reads and documents what the code 'actually does right now' (bugs included), systematically covers the happy path plus edge cases and error paths, and is strictly forbidden from modifying the code under test.
Migrating from Cursor to Claude Code / Codex: An Inventory-and-Kickoff Prompt
Has the agent automatically inventory your Cursor project (.cursorrules, .cursor/rules, .cursor/mcp.json), produce a step-by-step migration plan, and generate the corresponding CLAUDE.md or AGENTS.md, slash commands, and MCP config — so you're not stuck 'dumber than Cursor' on day one.
AI Agent Definition-of-Done Self-Check Spec
A Definition of Done template you can paste into any coding agent, turning 'what counts as done' into a checklist the agent must self-verify item by item: behavior meets acceptance criteria, tests/lint/typecheck/build all pass (or it states why they didn't run), risky changes come with a rollback plan, and a final 'verification story' is delivered. Puts an end to agents claiming 'done' while everything is actually broken.
Safe Multi-File Refactoring: Map Blast Radius, Then Batch and Verify
A large-refactor playbook for agents: first do a read-only survey of the 'blast radius' — which files, call sites, and tests are affected — then split the change into small batches, each preserving behavior, each run through its own tests, each its own atomic commit. Puts an end to 'change 40 files at once, then the build breaks and no one knows where to start fixing it.'