菜单
Enforces the repository commit message format whenever the user asks to commit, amend, squash, or create git history. Use before every git commit command to prevent malformed commit messages.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
This skill should be used when managing the file-based todo tracking system in the todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.
Use this skill when working in pi's Huddle Mode. Huddle Mode is a safe exploration mode where read operations are always allowed, write operations require user permission, and the gather_input tool enables structured multi-question elicitation with a rich TUI dialog.
Knowledge base lookups for acme
Helper utilities
Query previous pi sessions to retrieve context, decisions, code changes, or other information. Use when you need to look up what happened in a parent session or any other session file.
Query previous pi sessions to retrieve context, decisions, code changes, or other information. Use when you need to look up what happened in a parent session or any other session file.
| name | commit-message-format |
| description | Enforces the repository commit message format whenever the user asks to commit, amend, squash, or create git history. Use before every git commit command to prevent malformed commit messages. |
Use this skill for every request that creates or changes git commits.
This repository uses Conventional Commits:
<type>[optional scope]: <description>
Allowed type values:
feat - user-facing featurefix - bug fixdocs - documentation onlystyle - formatting only, no behavior changerefactor - code change that is neither a feature nor a bug fixperf - performance improvementtest - tests onlybuild - build system or dependency changesci - CI/CD changeschore - maintenance that does not fit another typerevert - reverts a previous commitRules:
The first line MUST match:
^(feat|fix|docs|style|refactor|perf|test|build|ci|chore|revert)(\([a-z0-9-]+\))?!?: .+
Use lowercase type and scope.
Put a space after the colon.
Use an imperative, concise description.
Do not end the subject with a period.
If there is a breaking change, use ! before the colon and explain it in the body.
git status --short.git commit.Good:
git commit -m "feat: add account switcher extension"
git commit -m "refactor: reorganize account switcher source layout"
git commit -m "docs: add pi package installation guide"
git commit -m "chore: add commit message skill"
Bad:
git commit -m "Prepare pi package installation"
git commit -m "updated files"
git commit -m "Fix bug."
If the latest local commit has the wrong format and has not been pushed, fix it with:
git commit --amend -m "<correct conventional commit message>"
Never create another malformed commit to fix a malformed commit.