Squashed 'docs/standards/playbook/' changes from c3f8137..25d895d

25d895d 🐛 fix(gitea_workflow): clean up temp repos after job steps
2bc3b11 🐛 fix(gitea_workflow): clean up temporary repo dirs in workflows
98c3f30 📝 docs(agent_rules): allow plan execution on current branch
16c7230 📝 docs(prompts): define custom verify layering
8efc4dd 🐛 fix(skills): quote commit-message description
bc8498f 🐛 fix(ci): install tomli for gitea tests
55cda3b 🐛 fix(tests): report missing toml parser clearly
c0729c7 🐛 fix(playbook): import Optional for cli compatibility
63e24bf 📦 deps(skills): sync thirdparty skills
d2f9356 🐛 fix(ci): isolate gitea workflow repos
588b81d 🐛 fix(ci): inline gitea workflow bootstrap
e0b1c3a ♻️ refactor(skills): standardize first-party skill contracts
2c5050d ♻️ refactor(skills): rename repo skills source dir
f049dfb 📦 deps(skills): drop duplicate first-party superpowers skills
234b335 ✨ feat(workflow): add superpowers planning and execution state tracking
c1702a6 📝 docs(markdown): format tracked markdown and drop stale templates
2325409 📝 docs(markdown): clarify optional markdownlint usage
214c44e 🔧 chore(markdown): add markdownlint baseline and lint fixes
a22b324 📝 docs(templates): add execution and memory-bank prompt templates
223a797 📝 docs(templates): update README for Claude Code and current features
4ac8672 📝 docs: simplify README + platform-agnostic tools + auto-create local rules
2431c9d 📝 docs: add claude_md config and use cross-platform paths
d64b248 📝 docs: fix README.md inaccuracies and add Claude Code info
c8d6bf2 🐛 fix(playbook): use relative paths in CLAUDE.md when not at project root
6518f0f ✨ feat(playbook): auto-create CLAUDE.md with path discovery
6ec9a45 ✨ feat(skills): add skill_link symlink support + platform-agnostic prompt
9f8b6b5 📝 docs: update README and config example for Claude Code support
79cff6c 📝 docs(skills): add Claude Code platform support
452c6f5 ✨ feat(playbook): auto-inject AGENTS.md into CLAUDE.md
e1dbf3c 🐛 fix(skills): remove dual-path from commit-message skill
f3a7259 🔧 chore(ci): use prepare_repo.sh in both workflows
da08212 🔧 chore(ci): extract prepare_repo.sh and clean up workflows
7ade85e 🗑️ remove(tsl): drop syntax_book/, data/ source and build script
f94dba0 ♻️ refactor(skills): update playbook.py and tests for thirdparty/ layout
b3df412 ♻️ refactor(skills): separate thirdparty skills into thirdparty/ subdirectory
64950e7 📦 deps(skills): sync thirdparty skills
a2e3cb0 ✨ feat(playbook): add no_backup deploy controls
8609d59 🐛 fix(docs): repair reference catalog source links
956da11 🐛 fix(playbook): publish hidden ci test fixes
3f67754 📦 deps(skills): sync thirdparty skills
08ca87b 📦 deps(skills): add karpathy thirdparty sync
96b705b 📝 docs(tsl): rebuild canonical syntax and routing manual
3ed5052 📦 deps(skills): sync thirdparty skills
60108dd 📦 deps(skills): sync thirdparty skills
da85d4e 🐛 fix(thirdparty): prune nested project snapshots
a2a697e 📦 deps(skills): sync thirdparty skills
9df610a 🐛 fix(thirdparty): exclude duplicated superpowers skills
33dd5bb 🐛 fix(thirdparty): preserve optional manifest fields
91b0ea7 🐛 fix(thirdparty): preserve manifest during snapshot update
2e26f98 🔧 chore(thirdparty): generalize skills sync pipeline
5b9c1e3 📦 deps(skills): sync superpowers
2f2d34a 📝 docs(readme): normalize subtree command spacing
62db7db 🐛 fix(ci): serialize superpowers update and sync
3463223 🐛 fix(ci): use literal superpowers sync paths
48f6de8 📦 deps(skills): sync superpowers
4b23529 🔧 chore(ci): merge superpowers update and sync workflow
a56d75b 📦 deps(skills): sync superpowers
84bcefa 🔧 chore(ci): use ci[bot] commit author name
00a07e5 📦 deps(skills): sync superpowers
7b84daf 🐛 fix(templates): enforce main loop progress tracking
51373d7 🔧 chore(ci): automate superpowers sync workflow
eaaa39c 🐛 fix(ci): prevent stale superpowers sync from restoring skills block
79755c6 📦 deps(skills): sync superpowers
836d878 📦 deps(skills): sync superpowers
8216c9f 📦 deps(skills): sync superpowers
9439505 🐛 fix(playbook): address reported repo issues

git-subtree-dir: docs/standards/playbook
git-subtree-split: 25d895d8b3f56624ccfe99ad7289e9eb49e0f316

skills/commit-message/SKILL.md

@@ -0,0 +1,98 @@
+---
+name: commit-message
+description: "Use when the user asks for help writing a commit message, wants emoji/type(scope): subject formatting, or asks to review staged changes before committing."
+---
+
+# Commit Message（提交信息建议器）
+
+## Overview
+
+Turn a staged diff into a commit recommendation that matches repository policy.
+Core principle: understand staged intent and commit boundaries before drafting the
+message.
+
+Authority source:
+
+- `docs/common/commit_message.md`
+- `docs/standards/playbook/docs/common/commit_message.md` (vendored playbook)
+
+## When to Use
+
+- The user asks to write or improve a commit message
+- The user wants emoji/type(scope): subject formatting
+- The user asks whether current staged changes should be split before commit
+- The user asks to review staged changes before running `git commit`
+
+## When Not to Use
+
+- No staged changes exist and the user expects a final commit message based on the
+  actual staged diff
+- The task is writing a PR title, release note, or changelog instead of a git
+  commit message
+- The user already provided an exact commit message and only wants it executed
+
+## Inputs
+
+- Current staging state (`git status --short`, `git diff --cached`)
+- Nearest applicable `commit_message.md`
+- Whether the user wants suggestions only or a command-ready final message
+
+## Procedure
+
+1. **Baseline the repo state**
+
+   - Inspect staged and unstaged state separately.
+   - If nothing is staged, stop. Explain that a staged-diff-based recommendation
+     is unavailable and ask whether files should be staged first.
+   - If only unstaged changes exist, stop before proposing a final message. Offer
+     a draft only if the user explicitly wants one.
+
+2. **Load the authority spec**
+
+   - Prefer the nearest `commit_message.md`.
+   - Reuse its type, emoji, scope, and body/footer conventions exactly.
+
+3. **Summarize staged intent**
+
+   - Read the staged diff at the smallest useful granularity.
+   - Identify the main logical change, affected areas, and whether the staged set
+     mixes unrelated work.
+   - If staged changes combine unrelated goals, strongly recommend splitting the commit
+     before drafting a single message. In other words, strongly recommend splitting
+     the commit instead of hiding multiple intents behind one subject.
+
+4. **Draft message options**
+
+   - Produce one recommended option and up to two alternatives.
+   - Keep the subject concrete, specific, and under the repo limit.
+   - Use body/footer only when they add real context such as motivation, impact,
+     verification, issue links, or breaking-change notes.
+
+5. **Finalize safely**
+
+   - Make it explicit whether the output is a suggestion or a final chosen message.
+   - Do not run `git commit` unless the user explicitly asks for execution after
+     reviewing the recommendation.
+
+## Output Contract
+
+- `Detected:` staged files summary, dominant intent, and split/no-split judgment
+- `Spec:` which `commit_message.md` was used
+- `Proposed:` Option A (recommended), Option B, Option C
+- `Optional body/footer:` only when justified
+- `Notes:` risks, ambiguity, or split advice
+
+## Success Criteria
+
+- The recommendation matches the staged diff rather than guessed intent
+- The selected format complies with the nearest commit policy
+- Split advice appears when staged changes are logically mixed
+- No commit command is executed unless the user asked for it
+
+## Failure Handling
+
+- If no staged diff exists, stop and explain the limitation instead of inventing a
+  final message
+- If the staged set is too broad or ambiguous, recommend splitting and explain why
+- If no local policy file is found, state the fallback convention before drafting
+- If repo state changes during review, rerun the staged summary before finalizing