commit-and-push

Commit staged changes using conventional commits and push them to the remote repository.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/bswrundquist/devtools --skill commit-and-push-bswrundquist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-and-push
Source: https://github.com/bswrundquist/devtools/tree/main/src/devtools/templates/claude/user/.claude/skills/commit-and-push
Command: npx skills add https://github.com/bswrundquist/devtools --skill commit-and-push-bswrundquist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of committing code changes using conventional commits and immediately pushing them to the remote repository, eliminating manual steps and potential delays.

Core Features & Use Cases

  • Automated Committing: Creates well-structured commits following the conventional commits specification.
  • Direct Pushing: Pushes committed changes to the remote repository without requiring user confirmation.
  • Use Case: After completing a feature or bug fix, you can use this Skill to commit your changes with a descriptive message and push them directly to your branch, ready for review or deployment.

Quick Start

Use the commit and push skill to commit and push your changes.

Frequently Asked Questions about commit-and-push

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

FAQPage Schema
How do I commit and push changes using conventional commits format?

To commit and push changes, this Skill commits staged changes using the conventional commits specification and immediately pushes them to the remote repository without requiring user confirmation.

What is the conventional commits format for git version control?

The conventional commits format structures commit messages with standardized prefixes to indicate change types. This Skill applies that specification automatically to staged changes during the code integration process.

Can I push committed changes to a remote repository without manual confirmation?

Yes, this Skill pushes committed changes directly to the remote repository without user confirmation, streamlining version control workflows where immediate and structured code integration is required.

How do I automate git commit and push steps for code integration?

Automating git commit and push requires staging changes first, then this Skill commits them using conventional commits format and pushes to the remote repository in sequence without manual intervention.

Does this git workflow require separate commit and push operations?

This Skill uses separate commit and push skills in sequence internally, committing staged changes with conventional commits format then pushing them to the remote repository automatically without user confirmation.

When should I use automated commit and push for version control?

Use automated commit and push when you need immediate and structured code integration after completing a feature or bug fix, and your changes are already staged and ready for the remote repository.