Stats
Actions
Tags
From qa
Reusable logic to commit & push safely — never push directly to main/master (auto-creates a feat/<slug> branch), commit per Conventional Commits with a Co-Authored-By trailer, push -u without force. Used by push-code and merge-request after the code is clean + build is green. Runs only when the user requests it.
How this skill is triggered — by the user, by Claude, or both
Slash command
/qa:commit-pushThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Reusable capability: get clean changes onto origin safely. Runs **only after** `review-audit` is clean of Critical and `build-verify` is green, and **only when the user requests it**.
Reusable capability: get clean changes onto origin safely. Runs only after review-audit is clean of Critical and build-verify is green, and only when the user requests it.
git branch --show-current.
main/master) → do NOT push directly. Create a feature branch feat/<slug> (inferred from the diff, or ask for a name if unclear) → git switch -c <branch>.git add the in-scope files; avoid adding junk/secret files (cross-check .gitignore — do not add results/tests/ run artifacts, .claude/qa-claude/.plugin.env, tokens, files containing secrets).test(order): them smoke flow tao don). End with the line:
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>git push -u origin <branch>. Remote rejects (branch behind remote) → git fetch + notify the user, do NOT force-push.Only commit/push when the user requests it (via command
/qa:push-codeor/qa:merge-request). Do not act on your own.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub hominhtuong/qa-claude-plugins --plugin qa