commit-to-git

Stage changes, bump patch version, commit, push, and tag releases.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/fivebucksventures/fiveagents-marketplace --skill commit-to-git-fivebucksventures
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-to-git
Source: https://github.com/fivebucksventures/fiveagents-marketplace/tree/main/plugins/link-skills/skills/commit-to-git
Command: npx skills add https://github.com/fivebucksventures/fiveagents-marketplace --skill commit-to-git-fivebucksventures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the end-to-end release workflow by staging changes, bumping the patch version in versions/version.ts, committing with a version-prefixed message, pushing to origin, and tagging the release.

Core Features & Use Cases

  • Stage changes and ensure a clean working tree before release.
  • Bump patch version only, updating versions/version.ts and VERSION_HISTORY.
  • Commit with a version-prefixed message, then push and tag for a formal release.
  • Use for daily automation or after sessions that modify code or docs requiring a new patch release.

Quick Start

Run commit-to-git to stage changes, bump the patch version, commit, push to origin, and tag the release.

Frequently Asked Questions about commit-to-git

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

FAQPage Schema
How do I automate git commit and release workflows for patch versioning?▼

Automate git commit and release workflows by staging changes, bumping the patch version in versions/version.ts, committing with a version-prefixed message, pushing to origin, and tagging the release.

What is the best way to bump patch versions and commit changes to git automatically?▼

Bump patch versions and commit changes automatically by running a workflow that updates versions/version.ts and VERSION_HISTORY, then commits with a version-prefixed message and pushes to origin.

Does this release workflow enforce patch-level versioning only?▼

Yes, this release workflow enforces patch-level versioning only, updating versions/version.ts and VERSION_HISTORY to ensure a clean working tree before pushing and tagging the formal release.

Can I use this git automation for both code and documentation modifications?▼

Yes, you can use this git automation for daily automation tasks or after sessions that modify code or docs requiring a new patch release, ensuring changes are staged and committed properly.

What steps does the end-to-end release workflow take before tagging a release?▼

The end-to-end release workflow stages changes to ensure a clean working tree, bumps the patch version in versions/version.ts, commits with a version-prefixed message, and then pushes and tags the release.

Why does the automated commit workflow update VERSION_HISTORY?▼

The automated commit workflow updates VERSION_HISTORY to maintain a record of patch-level versioning changes, ensuring that versions/version.ts and the release tag reflect the accurate state of the repository.