commit-and-push

Automate Git staging, semantic commit messages, and push with confirmation.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/cxm6467/caboose-cursor-tools --skill commit-and-push-cxm6467
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-and-push
Source: https://github.com/cxm6467/caboose-cursor-tools/tree/main/cursor-plugins/plugins/git-utils/skills/commit-and-push
Command: npx skills add https://github.com/cxm6467/caboose-cursor-tools --skill commit-and-push-cxm6467

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the Git commit and push process by automating staging, generating semantic commit messages, and ensuring user consent for sensitive operations.

Core Features & Use Cases

  • Automated Staging: Stages all modified and new files automatically.
  • Sensitive File Confirmation: Prompts for confirmation if sensitive files (e.g., .env, credentials) are detected.
  • Semantic Commit Messages: Generates commit messages following the conventional commit format (e.g., feat:, fix:).
  • Push to Origin: Automatically pushes the staged and committed changes to the remote repository.
  • Use Case: After completing a feature, you can simply say "/commit-and-push" to have the skill handle the entire Git workflow, ensuring clean and informative commit history.

Quick Start

Use the commit-and-push skill to stage all changes, generate a semantic commit message, and push to origin.

Frequently Asked Questions about commit-and-push

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

FAQPage Schema
How do I automate git commit and push with semantic commit messages?

Automating git commit and push involves staging modified files, generating conventional commit messages (e.g., feat:, fix:), and pushing to origin. This Skill handles that workflow automatically while prompting for user approval on commit messages.

How does sensitive file detection work during automated git staging?

Sensitive file detection scans staged changes for credentials or environment files like .env. Before proceeding with the git commit, the workflow pauses and requires explicit user confirmation to prevent accidentally pushing secrets to the remote repository.

Do I need Bash to automate version control tasks like staging and pushing?

Yes, you need Bash to execute the version control commands for staging, committing, and pushing changes. User interaction is also required to confirm sensitive file detection and approve the generated semantic commit messages.

What is the best way to generate conventional commit messages for git?

The best way to generate conventional commit messages is using an automated workflow that analyzes staged changes and creates semantic prefixes like feat: or fix:. This ensures a clean, informative version control history without manual formatting.

Can I use this to push all modified files to origin automatically?

Yes, you can push all modified and new files to origin automatically. The workflow stages all changes, generates a semantic commit message, requests your approval, and then pushes the committed changes directly to the remote repository.