Commit push

Skill tykisgod/quick-question/skills/commit-push

Batch commit all uncommitted changes and push to the remote repository.From its SKILL.md

Install

npx -y skills add tykisgod/quick-question --skill commit-push

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

skips confirmationTells the agent to proceed without asking first, 1 time: "qq-worktree.py closeout --auto-yes --delete-branch --pretty".
10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
runs commandsInstructs the agent to run 8 commands, including `qq-project-state.py --pretty` and 7 more.

SKILL.md

3.3 KB, 831 tokens by cl100k_base, as published. Nobody here has run it

Script path fallback: qq scripts are invoked as bare commands (e.g. unity-test.sh). If "command not found", use ${CLAUDE_PLUGIN_ROOT}/bin/<command> instead.

Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md).

Batch commit all uncommitted changes and push to the remote repository.

Steps

If qq-project-state.py is available, run it first:
```
qq-project-state.py --pretty
```
Interpret it like this:
- recommended_next == "/qq:commit-push" → normal ship path, continue
- otherwise → stop and tell the user the actual next step first
- if the user explicitly says to force the push anyway, note the risk and continue
Run git status -u and git diff --stat to view all uncommitted changes
Analyze the changes and group them by logical relationship (do not mix unrelated changes into the same commit):
- Feature code changes in one group (feat/fix/refactor)
- Asset files (prefabs, assets, scenes) in one group
- Config/docs in one group
- If all changes belong to the same feature, a single commit is fine
For each group:
- git add the relevant files (do not use git add -A; specify files individually)
- Write a commit message in conventional commit style
- Append Co-Authored-By: Claude Opus 4.6 <[email protected]> at the end of the commit message
After all commits are done, run git push
Worktree closeout — detect worktree type and close out:

Type A: EnterWorktree session (CWD is inside .claude/worktrees/):
- Identify the source branch: git log --oneline --all --decorate | head -5 or read the branch the worktree was based on
- Merge worktree branch back to source: git checkout <source-branch> && git merge <worktree-branch>
- Push source branch: git push
- Call ExitWorktree tool with action: "remove" to clean up and return to original CWD
Type B: qq-managed worktree (qq-worktree.py is available and isManagedWorktree=true):
- Prefer one-step closeout:
```
qq-worktree.py closeout --auto-yes --delete-branch --pretty
```
- If closeout refuses, inspect qq-worktree.py status --pretty
- Only fall back to separate merge-back / cleanup when debugging
Type C: Not in a worktree → normal path, stop after push

Exclusion rules

Do not commit:

.env, API keys, credentials, or other sensitive files
Files matched by .gitignore
.obsidian/ directory

Clear auto-pipeline (if active): qq-execute-checkpoint.py pipeline-clear --project . --status completed

Notes

If there are no changes at all, just inform the user
In hardening-style flows, treat /qq:commit-push as the end of the verified path, not the place to discover missing tests/review/doc drift
In any worktree (EnterWorktree or qq-managed), closeout belongs here, after verification and after push
For EnterWorktree worktrees: merge back via git, then ExitWorktree(remove)
For qq-managed worktrees: use closeout as the default path
Keep commit messages concise and focused on "what was done" rather than "which files were changed"
Check the style of recent commits and stay consistent

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 1 of the 12 instructions most pr commit review skills give in 831 tokens

Counted across 1,055 of the 1,911 authors here whose files we hold, read 2026-09-06

Use conventional commit message formathere, and in 150 of 1055, across 145 files
Announce skill usage at startin 78 of 1055
Use imperative mood for commit descriptionsin 54 of 1055, across 51 files
Add directory to gitignore if not ignoredin 52 of 1055, across 41 files
Use imperative mood for commit subjectin 52 of 1055
Run tests to verify clean baselinein 42 of 1055, across 32 files
Push branch to originin 40 of 1055, across 38 files
Verify worktree directory is ignored before creationin 39 of 1055, across 32 files
Delete branches after mergingin 38 of 1055, across 30 files
Create worktree with new branchin 37 of 1055, across 32 files
Wrap body text at 72 charactersin 36 of 1055, across 34 files
Auto-detect and run project setupin 35 of 1055, across 27 files

Said here and by no other author read

Run qq-project-state.py before proceeding
Use qq-worktree.py for managed worktree closeout
Clear auto-pipeline after completion

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.