commit

Automate safe git commits with pre-flight checks and structured messages.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/qmu/workaholic --skill commit-qmu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/qmu/workaholic/tree/main/plugins/core/skills/commit
Command: npx skills add https://github.com/qmu/workaholic --skill commit-qmu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git.

What problem does it solve?

Safe commits in multi-contributor environments ensure changes are intentional, reviewed, and properly attributed to contributors, preventing accidental or conflicting changes.

Core Features & Use Cases

  • Pre-flight checks: Inspect what will be committed and ensure only intended changes are included.
  • Review staged changes: Validate the staged set before committing to avoid cross-contributor churn.
  • Structured commit messages: Enforce a multi-part message format including motivation, UX change, and architecture notes.
  • Use Case: In a busy repo, run the script to commit a ticket with a descriptive title and a detailed message, preserving history and co-authorship.

Quick Start

Use the commit.sh script to create a safe, structured commit in your git repo, e.g.: bash path/to/commit.sh "<title>" "<motivation>" "<ux-change>" "<arch-change>" [files...]

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create safe git commits in a multi-contributor repository?

To create safe git commits, you run a shell script that inspects staged changes, enforces a structured commit message format, and attaches Co-Authored-By metadata to provide a robust and auditable history for collaborative projects.

What is a structured git commit message format for collaborative projects?

A structured git commit message format enforces multiple parts including motivation, UX change, and architecture notes. This ensures intentional changes are properly documented for code review and auditable history in multi-contributor environments.

How do I attach Co-Authored-By metadata to a git commit?

Attaching Co-Authored-By metadata to a git commit is automated during the commit workflow to properly attribute changes to multiple contributors. This preserves clear authorship history in shared software projects.

Do I need to install git to use this commit workflow script?

Yes, git is a required dependency. The script automates git commit workflows by running pre-flight checks, reviewing staged changes, and enforcing commit message formats directly within your repository.

How do I review staged changes before committing in a shared repo?

Reviewing staged changes before committing is handled through pre-flight checks that validate the staged set. This prevents cross-contributor churn by ensuring only intended changes are included in the final commit.