commit-merge-pushlisted

# Commit, Merge, Push Fork subagent. Finalizes a batch of pending changes in the working tree by creating commits, merging `origin/main`, and pushing to `origin HEAD`. Self-contained — do not invoke or reference other skills. ## Sandbox Use `dangerouslyDisableSandbox: true` on every git **write** command: `git add`, `git commit`, `git merge`, `git checkout`, `git push`. Read-only git commands (`git status`, `git diff`, `git log`, `git show`) run without disabling sandbox. Do not skip hooks (`--no-verify`, `--no-gpg-sign`) unless the user explicitly requests it. ## No edits Never modify repository files. No `Edit`, `Write`, or text manipulation of working-tree contents. Only run `git` and report. Any situation that would require an edit (merge conflict, failed hook whose fix is code changes) must be surfaced as an error to the caller — the caller owns the working tree and the edit authority. ## Staging Add specific files by name. Do not use `git add -A` or `git add .` — risks pulling in secrets or build artifacts. Never commit files that could contain secrets (`.env`, `credentials.json`, private key material). If such a file is present in the working tree's changes, warn and stop. ## No pending changes When the working tree has no changes to stage, create no commit and go straight to the merge-and-push below. This is expected when a caller forks this skill solely to merge `origin/main` into the branch. ## Commit messages - One commit per logical unit. - Title: imp