woocommerce-git-commit

Creates grouped git commits with conventional imperative messages for WooCommerce repository changes.

10.5k|10.7k|Updated Aug 9, 2011
One-click install
npx skills add https://github.com/woocommerce/woocommerce --skill woocommerce-git-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: woocommerce-git-commit
Source: https://github.com/woocommerce/woocommerce/tree/main/.ai/skills/woocommerce-git-commit
Command: npx skills add https://github.com/woocommerce/woocommerce --skill woocommerce-git-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing clear, convention-compliant commit messages and deciding how to group uncommitted changes is repetitive and error-prone. This Skill inspects your working tree, groups related changes, and commits them with well-formed messages following WooCommerce repository conventions.

Core Features & Use Cases

  • Change Analysis: Reads current branch, uncommitted changes, and diff stats to understand what was modified before committing.
  • Smart Commit Grouping: Splits unrelated changes into separate commits (e.g., changelog entries separate from source changes) while keeping related files in one commit.
  • Convention-Based Messages: Drafts verb-first imperative messages under 72 characters using verbs like Fix, Add, Update, Refactor, and Remove.
  • Use Case: After fixing a bug in the email editor and adding a changelog file, ask the Skill to commit your work; it produces one commit for the fix and a separate commit for the changelog entry.

Quick Start

Ask the assistant to commit your uncommitted changes with appropriate messages following WooCommerce conventions.

Frequently Asked Questions about woocommerce-git-commit

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

FAQPage Schema
How do I commit changes with conventional commit messages in git?

Stage specific files with git add and commit using a verb-first imperative message under 72 characters, such as "Fix get_item_downloads() not always returning an array". This Skill automates that by analyzing your diff and drafting compliant messages.

How should I split unrelated changes into separate git commits?

Group files changed for the same reason into one commit and split clearly independent changes, such as a bug fix mixed with an unrelated config change. Changelog entries should always be committed separately from source changes.

Does this Skill push commits to the remote repository?

No, the Skill never pushes to remote and never adds Co-Authored-By lines or self-attribution. It only creates local commits and shows git log output to confirm the results.

Why should I avoid git add -A when committing changes?

Blanket staging commands like git add -A or git add . can accidentally include unrelated or sensitive files in a commit. This Skill always stages specific files explicitly so each commit contains only intended changes.

Should lint checks run before or after committing PHP changes?

Lint checks should run before committing, not after. The woocommerce-dev-cycle skill handles PHP linting, and commits should wait until that lint passes since warnings block CI.