commit

Create conventional git commits with staged changes and optional push.

307|59|Updated Jun 2, 2024
One-click install
npx skills add https://github.com/spiriMirror/libuipc --skill commit-spirimirror
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/spiriMirror/libuipc/tree/main/.cursor/skills/commit
Command: npx skills add https://github.com/spiriMirror/libuipc --skill commit-spirimirror

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a well-formatted conventional commit locally to ensure consistent commit messages across a project.

Core Features & Use Cases

  • Format Changed Files: Normalize commit messages by enforcing the conventional commit structure before staging.
  • Stage and Commit: Stage changes safely and compose a compliant commit message without manual formatting.
  • Guarded Push: Optionally push only when explicitly requested, preventing accidental updates to remote branches.
  • Use Case: Ideal for feature work or maintenance tasks where standardized history improves collaboration and code review.

Quick Start

Format changed files, stage them, write a conventional commit message, and commit locally using the standard structure.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate conventional commit messages in my git workflow?

To automate conventional commit messages, this Skill stages your changes, writes a compliant message to a temporary file, and commits locally. It enforces the conventional commit structure to ensure consistent project history without manual formatting.

What is the best way to format git commits for consistent project history?

The best way to format git commits for consistent history is to enforce the conventional commit structure before staging. This standardizes messages during feature work and maintenance, ensuring code review and collaboration are improved across individual developers and teams.

Can I stage changes and write a conventional commit message without manual formatting?

Yes, you can stage changes and write a conventional commit message without manual formatting. The Skill safely stages changed files and automatically composes a compliant conventional commit message, eliminating the need to manually structure the text.

Does this conventional commit automation push to remote branches automatically?

No, this conventional commit automation does not push to remote branches automatically. It features a guarded push mechanism that only pushes your commits when explicitly requested, preventing accidental updates to the remote repository.

When do I need to use conventional commits for version control?

You need to use conventional commits for version control during feature work, bug fixes, and maintenance tasks. Standardized messages improve collaboration and code review for individual developers and teams using Git workflows who want a consistent project history.