菜单
Commit uncommitted changes with well-crafted messages following PooCommerce repo conventions. Use when the user says "commit", "commit changes", "commit this", "git commit", or "save my work".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/notmattpress/poocommerce --skill poocommerce-git-commit命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Add or modify PooCommerce backend PHP code following project conventions. Use when creating new classes, methods, hooks, or modifying existing backend code. **MUST be invoked before writing any PHP unit tests.**
Review PooCommerce code changes for coding standards compliance. Use when reviewing code locally, performing automated PR reviews, or checking code quality.
Guidelines for UI text and copy in PooCommerce. Use when writing user-facing text, labels, buttons, or messages.
正在显示 SKILL.md
基于 SOC 职业分类
| name | poocommerce-git-commit |
| description | Commit uncommitted changes with well-crafted messages following PooCommerce repo conventions. Use when the user says "commit", "commit changes", "commit this", "git commit", or "save my work". |
Commit uncommitted work with clear, conventional messages. Groups unrelated changes into separate commits when appropriate.
git branch --show-currentgit status --shortgit diff --statgit diff --cached --statFrom the dynamic context above, determine what changed:
Default to a single commit unless changes are clearly unrelated. Split only when:
Two files changed for the same reason = one commit. Don't over-split.
Use the current session context to understand what work was done and why. If motivation is still unclear after reviewing the diff and conversation, infer the best reasonable description from the diff and commit conventions.
Format — verb-first imperative, under 72 chars:
Fix get_item_downloads() not always returning an arrayAdd cache priming to AJAX downloadable searchUpdate email editor reset action label for consistencyRefactor order count cache refresh logicRemove deprecated payment gateway fallbackVerbs: Fix, Add, Update, Refactor, Remove, Restore, Bump, Prepare, Simplify, Improve, Replace
For changelog-only commits: Add changelog entries for [description]
Do NOT include issue/PR refs — GitHub adds those on squash-merge.
If $ARGUMENTS is provided, use it as guidance for the commit message.
State each proposed commit before executing:
Commit 1: Fix double margin-top in flex layout
files: src/Blocks/EmailEditor/Layout.php
src/Blocks/EmailEditor/styles.css
Commit 2: Add changelog entries for email editor fix
files: plugins/poocommerce/changelog/fix-email-margin
For each confirmed commit:
git add <specific files>
git commit -m "<message>"
Always stage specific files — never git add -A or git add ..
After all commits, show git log --oneline -n <number of new commits> to confirm.
git add -A or git add .poocommerce-dev-cycle skill handles that. Linting should be run before invoking this skill, not after. For PHP changes, don't commit until that skill's PHP lint has passed (warnings block CI).