CommitPush

Automate Git commits, branches, PRs, and version-control tasks with security checks.

7|1|Updated Jul 12, 2026
One-click install
npx skills add https://github.com/julianobarbosa/claude-code-skills --skill commitpush
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: CommitPush
Source: https://github.com/julianobarbosa/claude-code-skills/tree/main/skills/Git-skill
Command: npx skills add https://github.com/julianobarbosa/claude-code-skills --skill commitpush

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes workflows (resource) and references (resource) components.

What problem does it solve?

This sub-skill covers the end-to-end flow of staging changes, committing, and pushing to a remote, with security checks and push safety.

Core Features & Use Cases

  • Pre-push checks: Scan for secrets before pushing to remote.
  • Push with safety: Push with --force-with-lease and verification steps.
  • PR readiness: Prepare commits for PR review.

Quick Start

Commit changes and push to origin, ensuring remote integrity with force-with-lease.

Frequently Asked Questions about CommitPush

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent secrets from being pushed to a remote repository?

Pre-push secret scanning detects and blocks sensitive data before commits reach the remote. CommitPush automates this check as part of the push workflow, preventing accidental credential exposure.

What's the safest way to force push changes without overwriting remote work?

Force-with-lease is safer than force push because it verifies the remote hasn't changed since your last fetch. CommitPush uses this flag by default with verification steps to ensure safe, auditable execution.

How do I write commit messages that follow conventional commit format?

Conventional commits use a structured format (type: scope: description) for clarity and automation. CommitPush generates and validates these messages, ensuring consistency across your repository and enabling automated changelog and versioning.

Can I automate the entire Git workflow from staging to push with security checks?

CommitPush automates the end-to-end flow: staging changes, writing commits, scanning for secrets, and pushing safely. It integrates GitHub CLI operations and policy-based routing for built-in security and auditability.

Do I need GitHub CLI to use safe push and PR workflows?

GitHub CLI integration is built into CommitPush for PR-related operations, but core commit and push functionality works with standard Git. It enables additional features like PR readiness checks and GitHub-native operations when available.