Menu
Use when the user says: "ship it" or "commit push and PR". Commits, pushes, and creates a PR in one step.
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 this when the users says: "review existing feature","make this change"
Use when the user says: "extract learnings", "save this for next time", "remember this pattern", "consolidate memories", "dream", "clean up memories".
Use when the user asks about Claude token usage, wants to see how much they are spending on Claude, understand cache hit rates, review Claude Code workflow patterns, or get cost optimization recommendations.
Use when the user asks to recall, search, or continue past conversations. Triggers on "what did we discuss", "continue where we left off", "remember when", "as I mentioned", "you suggested", "we decided", "search my conversations", "find the conversation where", "what did we work on". Also triggers on implicit signals like past-tense references ("the bug we fixed"), possessives without context ("my project"), or assumptive questions ("do you remember").
Generate a commit message
Manage conversations and task context
| name | mine.ship |
| description | Use when the user says: "ship it" or "commit push and PR". Commits, pushes, and creates a PR in one step. |
| user-invocable | true |
git statusgit diff HEADgit branch --show-currentgit-default-branchgit remote get-url origin 2>/dev/nullShip the current changes: commit, push, and open a PR. Follow each phase in order.
Follow all steps in mine.commit-push exactly (read skills/mine.commit-push/SKILL.md and execute its full workflow). When that phase completes successfully — changes committed and pushed — continue to Phase 2 below.
mine.commit-push handles: branch creation, commit scope check, changelog, code review loop, integration review, local verification (tests + linting + test presence check), staging, committing, pushing, and WP archival reminder.
git-platform. If output is unknown, inform the user the platform is unsupported and stop. If github, use gh CLI. If ado, use az CLI.gh pr list --head <branch-name>az repos pr list --source-branch <branch-name> --status activegit-branch-log (uses closest remote branch as base)git-branch-diff-stat to see all code changes summary## Summary
<1-3 bullet points explaining what changed and why>
get-skill-tmpdir mine-pr to create a temp directory, then write the PR body to <dir>/body.md and use that path in subsequent commandsgh-pr-create --draft --title "..." --body-file <tmpfile>
az repos pr create --draft true --title "..." --description "<body content>" --source-branch <branch> --target-branch <default-branch>
--description "$(cat <tmpfile>)" — command substitution is broken in the Bash tool eval wrapper.CHANGELOG.md exists (use the one closest to the current working directory if multiple exist — not necessarily the repo root):
# (e.g., (#123)) — links to the PR(!123)) — links to the PR (# would link to a work item instead)gh pr view --json baseRefName --jq '.baseRefName'ado-pr show --json | jq -r '.targetRefName' | sed 's|refs/heads/||'git diff origin/<base>...HEAD -- <changelog-path> to identify lines added in this branch (use the path discovered in step 18, not a hardcoded CHANGELOG.md)- ) that does not already contain a PR reference ((#...) or (!...)), append (#<PR_NUMBER>) for GitHub or (!<PR_NUMBER>) for Azure DevOps to the end of the linechangelog: add PR #<NUMBER> for GitHub or changelog: add PR !<NUMBER> for Azure DevOpsCHANGELOG.md exists, suggest to the user that they add one to track notable changes per releasegh pr readyaz repos pr update --id <PR_ID> --draft falseImportant:
--body-file (GitHub) to avoid command substitutionAzure DevOps notes:
https://dev.azure.com/{org}/{project}/_git/{repo})--auto-complete or --delete-source-branch flags — just create the PRaz repos pr create command returns JSON; extract the PR URL from the response