cplisted

Branch and status: !`git status --short --branch` Changed files: !`git diff HEAD --stat || true` Recent subjects: !`git log --oneline -10 || true` Commit everything above on the current branch, then push. Do not switch or create a branch, even on main. 1. On the repository's default branch, run `gh api repos/{owner}/{repo}/rules/branches/<branch> --jq '[.[].type]'`. If it lists `pull_request`, the push would be refused: stop, commit nothing, and name `/cprw` instead. 2. Read the full diff (`git diff HEAD`) and every untracked file `git status` lists before writing anything. 3. Scan it for credentials, tokens, private keys, and any value that does not belong in this repository. If you find one, stop, commit nothing, and report what you found. 4. Stage the changes. Prefer explicit paths over `git add -A`. 5. Write a Conventional Commit `type(scope): description`, matching the subject style already in `git log`. Follow the `oss-writing` skill for the wording. $ARGUMENTS is a hint at what the change is about, not the message itself. 6. Commit, then `git push` (add `-u origin HEAD` when the branch has no upstream). 7. Report the subject, the short hash, and the branch pushed to. Split into several commits when the diff covers unrelated changes.