القائمة
Post-merge cleanup — update main, prune the remote, and print one paste-ready block of follow-up commands
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Commit remaining changes, push the branch, open a pull request, and run Codex review
Full development cycle — plan a feature, implement it, and open a PR
Process unhandled PR review comments on the current branch's open PR — answer questions, modify code, or push back
Like /develop, but skips test-writer invocation and post-impl verification (for repos without a test suite — see ADR-014 §12)
Run deep-learning experiments as disciplined hypothesis tests — frame the question, set up a self-contained per-experiment folder, launch training/eval runs (confirming before heavy GPU jobs), track metrics, analyze results against a baseline, and write a human-readable report with tables and plots. Use this whenever the user is doing experimental ML work: launching or preparing a training/finetuning/sampling/eval run, an ablation, or a hyperparameter sweep; saying things like "let's try X and see if it helps," "does this change improve FID/accuracy/loss," "compare these two runs/checkpoints," "track this experiment," "analyze the results," or "write up what we found." Trigger even when the user doesn't say the word "experiment" but is clearly testing whether a change moves a metric, or wants results organized, compared, or reported reproducibly.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
| name | finish-task |
| description | Post-merge cleanup — update main, prune the remote, and print one paste-ready block of follow-up commands |
| allowed-tools | Bash |
Clean up the local repository after a task branch has been merged.
Only git fetch and git checkout main run automatically. Everything else — force-deleting the merged branch, discarding stale worktree diffs, deleting other already-merged locals — is collected into a single paste-ready command block at the end, because the command allowlist and sandbox intentionally block those forms.
Sandbox fallback. If any command in this skill is blocked (allowlist, read-only mount, EBUSY, etc.), ask the user to run it on your behalf and continue from their result. Do not bypass the sandbox.
git fetch origin main:main
git checkout main
Fetching into main:main first makes the local ref match origin/main before checkout, so the squash-merged worktree usually needs no file writes on switch. If the checkout is blocked by the sandbox, apply the Sandbox fallback above — ask the user to run it on your behalf and continue once they confirm success.
Remember the branch you just left (from the checkout output or git reflog) as $PREV_BRANCH.
git fetch --prune
Build a list $CMDS by running each check below and appending the matching command. Do not execute any of them.
git status --porcelain lists any M/A/D entries for project files:
git restore --staged --worktree -- <file1> <file2> … (name each file explicitly; no ., -A, *, or globs).git branch -D $PREV_BRANCH.git branch --merged main | grep -Ev '^[* ]*main$' lists any:
git branch -d <name1> <name2> … (one command covering all).Emit the gathered commands as one fenced code block, in the order above:
Please run this in your terminal:
<all recorded commands, one per line>
If $CMDS is empty, print "No follow-up actions needed."