acp

Stage all changes, create a commit with a descriptive message, and push to the remote. Stack-aware.

Steps

1. Scan for secrets BEFORE staging anything. git add -A stages every non-ignored path, so a secret staged first is a secret the rest of this flow has to un-stage. List the paths git would stage — git status --porcelain --untracked-files=all (--untracked-files=all matters: plain --porcelain collapses an untracked directory to dir/ and would hide dir/.env) — and match the paths only against: .env and .env.* except the templates .env.example / .env.template / .env.sample; *.pem, *.key, *.p12, *.pfx, *.keystore, *.jks; id_rsa / id_ed25519 / id_ecdsa / id_dsa; credentials, service-account*.json, *.kubeconfig, .npmrc, .netrc. If anything matches, stop before staging and report the matching paths and the .gitignore / git rm --cached fix. Only continue if the user tells you explicitly to include that path.
2. git add -A to stage all changes.
3. Run git status and git diff --cached to understand what's being committed. If step 1 matched anything the user then authorised, exclude those paths from the diff — git diff --cached -- . ':(exclude)<path>' for each — because a bare git diff --cached prints the file's contents to the terminal and into this transcript. Deciding not to read the output is not the same as not emitting it, and the standing rule is that secrets are never printed or logged, not that they are printed and ignored.
4. Write a concise, descriptive commit message based on the changes. If $ARGUMENTS is provided, use it verbatim as the commit message instead.
5. Commit.
6. Decide how to push:
   • If the current branch is part of a gh stack (run gh stack view and check it doesn't error), run gh stack submit — it both pushes the stack and creates/updates the PRs in one step, so the PR list and the remote tips stay aligned. (gh stack push only pushes branches; PRs would still update via the new tip, but submit also reconciles PR titles/descriptions with stack ordering, which is what we want after a commit.)
   • Otherwise, git push on the current branch (add -u origin <branch> if the branch has no upstream).
7. Report the commit SHA and, for stacked branches, the PR URL from gh stack view. If the diff you read in step 3 suggests a follow-up review pass would catch something — substantial logic changes, a new module, a refactor across several files in one area, a large delete — append a one-line "consider /verify" / "consider /grill" / "consider /scan on <dir>" / "consider /techdebt" suggestion tied to the actual signal. Skip the suggestion entirely for doc-only, config-only, dep-bump, or formatting commits. Don't run the suggested command — the user picks.