cyberneticlibrary

Commit and push branch

cpcommandsetup L217,464
alirezarezvani/claude-skills
What it does

Commit and push changes after local quality checks pass

Best for

Enforcing local lint/test/security checks before pushing, then triggering and awaiting remote CI-quality-gate validation.

Inputs
  • · Staged working tree changes
  • · .github/commit-template.txt (Context/Testing/Reviewers blocks)
  • · Current branch name (git branch --show-current)
Outputs
  • · Pushed commits to origin/CURRENT_BRANCH
  • · Triggered ci-quality-gate workflow
  • · Workflow run hash and status output
Requires
  • · git add (staging)
  • · git commit (Conventional format)
  • · git push origin $(git branch --show-current)
  • · gh workflow run ci-quality-gate.yml
  • · gh run watch (monitor workflow)
Preconditions
  • · /review passed locally
  • · All changes staged and diff-reviewed
  • · ci-quality-gate.yml exists in .github/workflows/
  • · GitHub CLI (gh) configured with repo push permission
Failure modes
  • · commitlint rejects commit message (user must fix and retry)
  • · Push fails if branch tracking not set (needs -u on first push)
  • · ci-quality-gate workflow fails silently if not watched
  • · PR opened before workflow completes (breaks governance)
  • · AI attribution strings in commit body (explicitly forbidden)
Trust signals
  • · /review prerequisite blocks unvetted changes
  • · Conventional Commit message format enforced via commitlint
  • · commitlint failure handling documented (fix and retry)
  • · Workflow triggered and watched (not fire-and-forget)
  • · Explicit wait-for-workflow-finish rule before PR creation
  • · No AI attribution in commits