원클릭으로
checkpoint
Imported from everything-codex command checkpoint
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Imported from everything-codex command checkpoint
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
AI-native code annotation protocol that encodes intent, risk, dependencies, constraints, and test expectations in machine-parseable comments.
Professional Codex-native multi-agent code review with confidence scoring
架构规划专家 - 使用 Codex 本地上下文、仓库证据和只读 child agent 进行大型系统架构设计与规划。
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
Use when the user explicitly asks for Conductor, wants track/spec/plan/review artifacts on disk, or needs long-lived project context management. Prefer start-dev for small or one-off tasks. If Conductor is not configured in the project, start with setup.
| name | checkpoint |
| description | Imported from everything-codex command checkpoint |
| version | 0.1.0 |
| source | fork |
| checksum | 62622f7bbbaae8df8dad4280cb81eaad46425aabc59e3360a16ac3f32bd37e51 |
| updated_at | "2026-02-11T01:29:16.000Z" |
| layer | utility |
Codex supports native subagents. Delegate with spawn_agent, coordinate with send_input, collect via wait_agent, and clean up with close_agent.
Execution preference:
[ANALYST]/[ARCHITECT]/[EXECUTOR]/[REVIEWER] structure in a single response.Minimal orchestration pattern:
spawn_agent -> send_input (optional) -> wait_agent -> close_agent
Create or verify a checkpoint in your workflow.
$checkpoint [create|verify|list] [name]
When creating a checkpoint:
$verify (quick mode if supported) to ensure current state is clean.codex/checkpoints.log:echo "$(date +%Y-%m-%d-%H:%M) | $CHECKPOINT_NAME | $(git rev-parse --short HEAD)" >> .codex/checkpoints.log
When verifying against a checkpoint:
Read checkpoint from log
Compare current state to checkpoint:
Report:
CHECKPOINT COMPARISON: $NAME
============================
Files changed: X
Tests: +Y passed / -Z failed
Coverage: +X% / -Y%
Build: [PASS/FAIL]
Show all checkpoints with:
Typical checkpoint flow:
[Start] --> $checkpoint create "feature-start"
|
[Implement] --> $checkpoint create "core-done"
|
[Test] --> $checkpoint verify "core-done"
|
[Refactor] --> $checkpoint create "refactor-done"
|
[PR] --> $checkpoint verify "feature-start"
$ARGUMENTS:
create <name> - Create named checkpointverify <name> - Verify against named checkpointlist - Show all checkpointsclear - Remove old checkpoints (keeps last 5)