菜单
Provides educational guidance on writing good git commit messages. Activates when users ASK QUESTIONS about commit message formats, styles, conventional commits, classic commits, atomic commit principles, or git best practices. Does NOT activate when users want to PERFORM a commit (use the commit-action skill instead).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Review and clean up commits before pushing. Uses planner/executor split: reads commits inline, authors final messages in saved style, replays via `git rebase --exec` with GIT_EDITOR=true so no editor opens. Detects logical clusters of granular TDD commits and proposes collapsing them into one logical commit. Auto-amends drifted subjects on revalidation. Activates on: "review commits", "clean up commits", "prep for push", "squash these commits", "finalize commits", "merge branch to main", "clean up my commits before pushing", "review before push".
Validate commits before pushing. Runs six deterministic checks: clean worktree, tests pass, no AI co-author leaks (Claude, Anthropic, GPT, OpenAI, Copilot), no conflict markers, no squash/fixup residue, and subject lines conform to the configured style (classic or conventional). Activates on: "validate commits", "check commits before push", "any AI leaks", "check for co-author", "are my commits clean", "validate before pushing", "check commits".
Triggers when user wants to PERFORM a git commit action. Activates on phrases like "commit these changes", "commit this", "let's commit", "make a commit", "create a commit", "commit my work", "commit the changes", "time to commit", "ready to commit", "commit what I've done", "save my changes" (git context), "commit for me", "do the commit", "commit now", "go ahead and commit", "please commit", "can you commit", "would you commit"
Initialize and manage Nix flake development environments with auto-detection and security tooling
Guardrail for efficient refactoring. IDEs use AST-based semantic refactoring (instant, atomic, accurate). AI uses text-based pattern matching (slower, sequential, error-prone for structural changes). This skill provides decision criteria for when to delegate to IDE vs proceed with AI. Consult before: renames across files, moving packages, changing signatures, extracting interfaces, or any multi-file coordinated structural change.
This skill should be used when the user wants to create a visual sketch, diagram, or mind map from captured content like articles, videos, or blips. Enables creating Excalidraw visualizations from jot captures.
| name | commit-style |
| description | Provides educational guidance on writing good git commit messages. Activates when users ASK QUESTIONS about commit message formats, styles, conventional commits, classic commits, atomic commit principles, or git best practices. Does NOT activate when users want to PERFORM a commit (use the commit-action skill instead). |
This skill provides educational context about writing effective git commit messages.
Activate this skill when the user asks questions about:
Do NOT use this skill when the user wants to perform a commit. The following are handled by the commit skill:
For action requests, the commit skill invokes the /commit workflow.
This plugin supports multiple commit styles. For detailed rules, examples, and anti-patterns, read the style files in the styles/ directory:
styles/classic.md) - Traditional git commit style following the "7 Rules"styles/conventional.md) - Structured format for automation| Aspect | Classic | Conventional |
|---|---|---|
| Subject case | Capitalized | lowercase |
| Type prefix | No | Yes (feat:, fix:, etc.) |
| Max subject | 50 chars | 50 chars (including type) |
| Body wrap | 72 chars | 72 chars |
| Mood | Imperative | Imperative |
| Automation | Manual | Changelog/semver friendly |
An atomic commit represents a single, complete, coherent unit of work.
/commit to generate properly formatted messagesFor comprehensive rules, examples, and anti-patterns for each style, read the corresponding file in the styles/ directory. The style files are the authoritative source for formatting rules.