Menu
Use when the user says: "commit and push". Commits and pushes changes to the current branch.
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
Use when the user says: "clean code check", "style review", "LLM smell check", "code hygiene", "nitpick this", "style check", "find style sins", "nitpicker review", "anal retentive review", "exhaustive style review", "no-filter style report". Dispatches three parallel stylistic checkers — llm-checker (training-bias patterns), lazy-checker (deferred debt), and nitpicker (style hygiene) — and consolidates findings into a report organized by checker with a Summary section for orchestration consumption.
Use when the user says: "review my changes", "run the reviewers", "code and integration review", "readability review", "maintainability review", "sniff test this", "WTF check", "code smells", "is this code any good", "fresh eyes on this branch", "review this directory", "check this module", "review this skill", "review these instructions". Dispatches three parallel reviewers — code, integration, and a readability pass for code; consistency, instruction quality, and writing quality for instruction files — and consolidates findings into one prioritized report.
Use when the user says: "spec this out", "help me define what I want to build", "interview me about this idea", "design this change", "write a design doc", or needs to define WHAT and HOW to build something. Proportional discovery interview + codebase investigation → design.md.
Use when the user says: "draft a plan", "create work packages", "generate WPs", "review this plan", or "check the plan". Turns a design doc into task files and validates them against a traceability-focused checklist.
Use when the user says: 'close gaps in this design', 'fill gaps in the spec', 'lightweight design review', 'gap-close this doc', 'completeness review', or wants to verify a doc has all required content before implementation.
Use when the user says: "ship it" or "commit push and PR". Commits, pushes, and creates a PR in one step.
| name | mine-commit-push |
| description | Use when the user says: "commit and push". Commits and pushes changes to the current branch. |
| user-invocable | true |
git statusgit diff HEADgit branch --show-currentHandles the "commit & push with quality gates" phase — standalone, and as Phase 1 of mine-ship (which adds PR creation).
Based on the above changes:
git-default-branch to check), create a new branch first.integration-reviewer + wtf-reviewer in parallel on the final diff — protocol and exit conditions as specified in rules/common/git-workflow.md (Mandatory Code Review Before Commit). If the same CRITICAL or HIGH findings recur and cannot be auto-fixed, defer to the user — do not proceed to commit.rules/common/commit-conventions.md (Local Verification Before Commit — discovery order and 3-attempt retry limit), plus one gate that file doesn't cover:
references/common/testing.md):
Review the branch diff (git diff --name-only against the default branch). If the diff contains new or changed source files but zero changes in test files (no files matching common test patterns like test_*, *_test.*, *_spec.*, __tests__/), mention this to the user and ask whether to proceed or stop to write tests. Advisory, not a hard block — the user decides.rules/common/git-workflow.md (Task File Cleanup). If cfl archive exits non-zero, stop and report the error to the user — do not proceed to commit. Include the resulting deletions and design.md changes in the commit.get-skill-tmpdir mine-commit to create a temp directory, then write the message to <dir>/message.md and run git commit -F <dir>/message.md — cleaner than embedding a heredoc on the command line. For simple one-line messages, git commit -m "..." is fine.-u flag only if you just created a new branch).