菜单
Commit-and-push workflow with validation. Use when asked to "cap", "commit and push", or "ship it".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Write an implementation plan as a markdown file, then immediately serialize it to a timestamped YAML task file in .ctx/tasks/. Use before touching any code when given a spec or approved design.
Design-first workflow for new features, components, or architecture decisions. Use before writing any code — get explicit approval on a design first.
Systematic debugging for Rust. Use before proposing any fix — establish root cause first, then write a failing test, then fix.
Dispatch parallel subagents for independent tasks. Use when 2+ tasks have no shared state or sequential dependencies.
Task graph management for a session. Use to create tasks, track progress, execute the next unblocked task, or manage dependencies between work items.
Test-driven development workflow for Rust. Use before writing any implementation code — write a failing test first, then implement, then refactor.
| name | godmode-cap |
| description | Commit-and-push workflow with validation. Use when asked to "cap", "commit and push", or "ship it". |
Run the full validation gate, commit, and push in one pass.
cargo check --workspace
cargo nextest run --workspace
cargo clippy --workspace -- -D warnings
cargo fmt --all --check
cargo check or tests fail — stop. Report failures. Do not commit broken code.cargo fmt --check fails — run cargo fmt --all to fix, then continue.git add -A
git diff --cached --stat
Review staged files. If unrelated changes are staged, report and ask before proceeding.
Use Conventional Commits:
<type>(<scope>): <summary>
Types: feat, fix, refactor, test, docs, chore, ci
Scope: crate name or module. Derive message from the staged diff — do not ask the user.
git branch --show-current
If output is main and user did not explicitly ask to commit to main — stop and report.
git commit -m "<message>"
Hook failure recovery: read the hook output, identify the exact rule. False positive →
add minimum exclusion and retry once. Real issue → fix, re-stage, retry once. Still failing
after one retry → stop and report. Never use --no-verify.
git push
If push is rejected (non-fast-forward): report to user. Do not force-push without explicit instruction.
If a godmode task is currently running:
godmode task done <task-id> --commit <sha>
--no-verify.main directly — verify with git branch --show-current first.