What problem does it solve? Committing code often skips project-knowledge updates and produces inconsistent commit messages. This Skill enforces a safe, structured Git commit workflow that checks whether changed modules are covered by the Flow2Spec knowledge base, generates a standardized emoji + Conventional Commits message, and commits only explicitly listed files. ## Core Features & Use Cases - Safe commit execution: Reads git status and git diff, separates staged/unstaged/untracked files, blocks on unresolved merge conflict markers, and never uses git add -A, --no-verify, or auto-push. - Knowledge-base coverage check: Verifies changed modules against .Knowledge/topics/ and .Knowledge/stock-docs/, auto-merges pending kb-delta.json when possible, and skips the check for quick commits, doc-only changes, or a sync within the last 30 minutes. - Standardized commit messages: Generates a first line in the form <emoji> <type>[(scope)]: <summary> (e.g., 🐛 fix(auth): 修复登录态丢失) based on the actual diff, then commits immediately after displaying it. - Use Case: After finishing a feature, ask the agent to commit; it inspects the diff, warns if the new module is not yet in the knowledge base, drafts 🚀 feat: 支持活动缓存预热, stages only the changed files, and commits. ## Quick Start Ask the agent to commit my current code changes with f2s-git-commit, or say "快捷提交" to skip the knowledge-base coverage check.
