菜单
Review git commits for quality, clarity, and best practices before pushing. Checks commit message format, diff size, test coverage signals, and common mistakes. Use when reviewing commits, before pushing, when asked to "check my commits", "review changes", or "is this ready to push".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | commit-review |
| description | Review git commits for quality, clarity, and best practices before pushing. Checks commit message format, diff size, test coverage signals, and common mistakes. Use when reviewing commits, before pushing, when asked to "check my commits", "review changes", or "is this ready to push". |
Systematic review of git commits for message quality, diff hygiene, and common mistakes before pushing.
Version: 1.0.0 Category: Skills Author: @sample-creator
Before responding to any invocation:
${CLAUDE_SKILL_DIR}/references/review-criteria.md
— Contains: commit message format rules, diff size thresholds, anti-patterns${CLAUDE_SKILL_DIR}/examples/good-vs-bad.md
— Contains: 5 examples of good commits vs. problematic commits| Input | Required | If Missing |
|---|---|---|
| Commits to review | Yes | Ask: "How many recent commits should I review? Or give me a range (e.g., HEAD~3..HEAD)" |
| Branch context | No | Default: current branch. State assumption. |
| Strictness level | No | Default: standard. Options: relaxed (personal project), standard, strict (team/OSS) |
For each commit in the review scope:
Step 1 — Message Quality
type: subject or type(scope): subject)Step 2 — Diff Analysis
Step 3 — Anti-Pattern Scan
console.log, debugger, print("HERE"))Step 4 — Quality Signal
| Mode | When to Use | What Changes |
|---|---|---|
relaxed | Personal project, rapid iteration | Skip message format, allow larger diffs |
standard | Team project (default) | Full review, balanced feedback |
strict | Open source, shared codebase | Enforce conventional commits, flag all anti-patterns |
COMMIT REVIEW — {branch} ({N} commits)
Commit 1: {short hash} — {subject}
Message: PASS | WARN | FAIL — {note}
Diff: {files} files, +{added}/-{removed} lines — {assessment}
Patterns: {anti-patterns found or "clean"}
Signal: {quality signals detected}
...
SUMMARY
Reviewed: {N} commits
Ready to push: {yes/no}
Issues: {count} ({critical}, {warnings})
Recommendation: {specific action}
Before delivering the review:
If any check fails: complete the review before delivering.
console.log but ignoring hardcoded API keys/publish (review commits before publishing a myClaude product)Show all available Studio Engine commands with descriptions. Displays command list organized by category, current edition features, and quick start guide. Use when the creator asks "help", "commands", "what can I do", or "how does this work".
Display Studio Engine status dashboard. Shows version, edition, creator profile, products with scores, and stale warnings. Use when: 'status', 'dashboard', 'show my products', or at session start.
Scaffold a new product with MCS-1 valid structure and WHY comments. Supports all 13 types. Use when the creator says 'new skill', 'create', 'scaffold', 'start building', or wants to start a new product.
Guide content filling for scaffolded products. Walks sections, asks domain questions, writes expertise into files. Use after /create in 'scaffold' state, or when the creator says 'fill', 'add content', or 'help me complete this'.
Research a domain before building products. Tests Claude's baseline knowledge, identifies gaps, scans the marketplace, runs deep research, and recommends the optimal product setup. Use when: 'scout', 'research domain', 'what should I build for', 'analyze domain', or before /create for any non-trivial product.
Run MCS quality validation on products in workspace/. Three-tier system: MCS-1 structure, MCS-2 quality + anti-commodity, MCS-3 deep review. Returns scored reports with fix instructions. Use when: 'validate', 'check quality', or before publishing.