Menu
Push committed work, open a PR targeting the correct base branch, monitor CI, and merge when ready.
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.
Copy processed MP3s and WAVs to NAS storage. Use after Apple Music import or when re-archiving corrected files.
Move processed ZIPs to archive and clean up extraction folders. Use after album processing is complete.
Copy finished MP3s into Apple Music via the auto-import folder and verify the album lands correctly. Use once metadata is finalized and the user wants tracks added to their library — e.g. "add this to Apple Music" or "import these tracks" — even if they don't say "auto-import" explicitly. Also use to diagnose a bad import, e.g. "it showed up as separate tracks instead of one album."
Inspect and update MP3 tags: genre, artist, album, track count, compilation flag. Use when checking or fixing music file metadata — including diagnostic questions like "why do these show up as separate tracks" or "is this folder's metadata consistent," not just explicit tag-editing requests.
End-to-end processing of downloaded music purchases: extract ZIPs, verify metadata, import to Apple Music, archive to NAS, clean up. Use when processing new music downloads.
Reclaim local disk by offloading cloud-backed Apple Music downloads. Audit iCloud status, build an offload playlist that protects your DJ crates and lossless files, then Remove Download. Use when the Mac is low on disk.
Based on SOC occupation classification
| name | push |
| description | Push committed work, open a PR targeting the correct base branch, monitor CI, and merge when ready. |
Push committed work, open a PR targeting the correct base branch, monitor CI, and merge when ready.
Determine the base branch from the current branch name:
develop, hotfix/*, or release/* → base is maindevelopReview commit count — run git log origin/<base>..HEAD --oneline. Since this project
squash-merges, lean toward 1–3 commits per PR. WIP checkpoints, format commits, and
implementation-journey fixes should be squashed away before pushing. See the commits skill
for guidance.
Ensure the branch is up-to-date with the base:
git fetch origin <base>
git log HEAD..origin/<base> --oneline # if output, merge before pushing
git merge origin/<base>
Push the branch to origin.
Create a PR with an explicit base — use the commits skill for title and description format:
gh pr create --base <base> --title "<title>" --body "<body>"
Monitor CI — report each check's status as it completes.
When all CI checks pass, report the result and ask before merging.
Merge and clean up — order is critical when working from a worktree:
Step A — capture context and merge while CWD is still valid:
MAIN_REPO=$(git worktree list --porcelain | head -1 | sed 's/^worktree //')
WORKTREE_PATH=$(git rev-parse --show-toplevel)
BRANCH=$(git branch --show-current)
gh pr merge --squash # feature/fix branches → develop
# Exception: release promotion PR (develop → main) must use --merge, not --squash
Step B — run the cleanup script. The skill base directory is shown at the top of this file when loaded — use it to locate the script:
bash "<skill-base>/scripts/post-merge-cleanup.sh" "$MAIN_REPO" "$WORKTREE_PATH" "$BRANCH"