メニュー
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コマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？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).