Menu
Use for branching, commit, PR, merge, rebase, and release discipline. Adapts Git workflow guidance to codex-max multi-repo boundaries.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
MANDATORY: Run appropriate validation tools after EVERY code change. Do not finish a task until the code is error-free.
Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring 5+ tool calls. Supports automatic session recovery after /clear.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Legacy compatibility alias for task-router-lite. Keeps older codex-max references working while using a thin Phase PLAN routing model.
Thin Phase PLAN router for codex-max. Select at most one primary execution skill and one optional secondary skill from the installed local skill surface.
Use when a significant technical decision should be recorded with context, alternatives, and consequences so the reasoning survives beyond the current session.
| name | git-workflow |
| description | Use for branching, commit, PR, merge, rebase, and release discipline. Adapts Git workflow guidance to codex-max multi-repo boundaries. |
| risk | safe |
| source | codex-max |
| origin | ECC-adapted |
| date_added | 2026-04-19 |
Use git-workflow when the task is mainly about git process rather than code behavior.
Examples: branching strategy, commit style, PR hygiene, merge/rebase choice, release steps, or conflict-handling discipline.
This workspace is multi-repo. Therefore:
Prefer a simple, reviewable workflow unless the repo clearly needs something more complex. Short-lived branches are usually the best default.
Prefer clear, scoped commit messages that explain the intent of the change. A conventional-commit style is acceptable when the repo already uses it.
A good PR should state:
When this skill is used, the result should include:
verification-before-completion — ensure evidence exists before calling work readyplanning-with-files — when git workflow is part of a larger multi-step tasktask-router-lite — routes here when git process is the main subject