菜单
Safely pull the local Codex configuration checkout from https://github.com/marcocello/dot-codex. Use when the user asks to pull, update, refresh, or get the latest dot-codex repo, Codex skills, scripts, AGENTS.md discipline, or local Codex configuration from marcocello/dot-codex.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Review a target app or project's feature specs, proof plans, proof evidence, successful tests, evaluator results, and user corrections to suggest app-specific improvements, new features, proof hardening, and reusable harness lessons without applying changes. Use when Codex should manually analyze whether features, proofs, and successful checks make sense and produce suggestions for the app/project or for dot-codex harness evolution.
Turn an overall app description into a sharper app brief, bootstrap repo-level docs, create a series of features, executable proof packages, and the feature queue. Use for greenfield work when the user has an app idea and wants Codex to initialize the project before returning to feature execution. Use the `research` skill when assumptions need external evidence.
Execute a feature queue, one feature, or a stubborn issue fix through a Codex Goal with explicit PROOF.md verification, evaluator judgment, bounded repair, and queue progress updates. Use when the user asks for autonomous execution, keep-going-until-done behavior, queue completion, or repeated repair after coding-feature-execute or coding-repair.
Evaluate whether a completed feature or issue fix is actually done using a read-only skeptical review of FEATURE.md, PROOF.md, primary proof results, gate results, architecture fit, and anti-gaming risks. This is the done judge, not the test runner. Use after coding-feature-execute, coding-repair, or coding-autonomous-execute before marking work complete.
Implement one feature end-to-end in Codex App using FEATURE.md for desired behavior, PROOF.md for done criteria, existing repo skills, red/green proof-first work, deterministic validation, mandatory backend/frontend/WordPress domain-skill handoff, and bounded repair. Use when a feature contract and proof contract are ready or need to be made ready before delivery.
Review FEATURE_DIR/FEATURE.md and FEATURE_DIR/PROOF.md before non-trivial implementation for ambiguity, edge cases, testability, proof quality, and architecture conflicts without adding framework phases.
| name | pull-codex-config |
| description | Safely pull the local Codex configuration checkout from https://github.com/marcocello/dot-codex. Use when the user asks to pull, update, refresh, or get the latest dot-codex repo, Codex skills, scripts, AGENTS.md discipline, or local Codex configuration from marcocello/dot-codex. |
Use this skill to update the local marcocello/dot-codex checkout that supplies Codex skills, scripts, and configuration.
Run the bundled script from this skill:
python skills/pull-codex-config/scripts/pull_codex_config.py
If the script reports local changes, stop and show the user the listed paths. Do not stash, reset, or overwrite those changes unless the user explicitly asks.
If the script succeeds, tell the user whether the repo was cloned or fast-forwarded.
If new or changed skills are expected in the current Codex session, mention that the UI or thread may need a reload before newly pulled skill metadata is visible.
https://github.com/marcocello/dot-codex.--repo-dir, when provided.DOT_CODEX_REPO, when set.CODEX_HOME, when it points at a Git checkout.$HOME/software/marcocello/dot-codex.origin remote, refuse local changes by default, then run a fast-forward pull from origin/main.--repo-dir PATH: pull into a specific checkout.--repo-url URL: override the remote, mainly for tests or mirrors.--branch NAME: pull a branch other than main.--allow-dirty: allow Git to attempt the pull despite local changes. Use only after explicit user approval.