cc-status

CC Status

Use this skill when the user explicitly requests status, wants to view Codex configuration status, or troubleshoots whether changes took effect after sync.

Do not use for:

• Status diagnostics for Claude or Gemini
• Formal code review
• Changing project code implementation

Core approach

1. Look at both the in-project .codex/ authoritative source and the user-level ~/.codex/、~/.agents/skills/ deployment artifacts.
2. Check whether the global entry points are complete:AGENTS.md、rules/、instructions/、skills/、*.config.toml profiles。
3. Check whether AGENTS.md contains managed blocks, and whetherrules/、instructions/、skills/ and profiles retain the manifest.
4. Check whether the codex CLI is available, and report the version.
5. If codex execpolicy check is available, sample-verify whether the current rules' allow/prompt/forbidden meets expectations.
6. Additionally check whether the current project has the prerequisites for new-feature task persistence: whether the in-project .codex/tasks/、.codex/tasks/archived/、.codex/templates/ exists.
7. Additionally check .codex/tasks/ active tasks in the root directory: the current main task, candidate tasks, interruption points, the most recent update time, and whether multiple tasks are simultaneously marked as 进行中 conflict.
8. Additionally check whether the current project root directory AGENTS.md exists, whether it contains the AUTO:* automatic block, and whether the project-level context is obviously missing.
9. If the in-project count and the user-level count are inconsistent, first determine whether the sync script has not yet been run.
10. If the in-project skeleton is complete but tasks still cannot be persisted, first determine whether the current Codex session's sandbox / workspace scope only covers a restricted directory, rather than the project root directory itself being unwritable.
11. Output status, gaps, and next steps; do not give vague environmental descriptions.

Output requirements

• Clearly distinguish between the "project authoritative source" and the "user-level effective configuration"
• Clearly distinguish between "files have been synced" and "rules have taken effect"
• Clearly distinguish between "configuration status" and "task status"
• Report missing items, count discrepancies, managed block anomalies, and obvious anomalies
• If the current project lacks .codex/tasks/ or .codex/templates/, clearly indicate that this will affect new-feature persistence, and recommend running $project-init or $project-scan
• If the current project lacks the root directory AGENTS.md, or AGENTS.md is clearly missing the project overview / automatic block, clearly recommend running $project-scan
• If there are active tasks, report the current mainline, candidate tasks, blocked or interrupted status, and which one is recommended to resume first
• If multiple tasks are found to be simultaneously in 进行中, clearly point out that this is a status conflict, and recommend first using cc-task-state to converge
• If no problems are detected, directly state that the status is normal
• If sync is suspected not to have been run, clearly recommend running tools/sync-config.sh
• If the skeleton is complete but task writes still fail, you must clearly distinguish between "the project root directory is indeed unwritable" and "the current session is still executing within a restricted sandbox / workspace scope"

Expand as needed

• Check items:references/status-checks.md