菜单
[Git] Use when asked to "commit", "stage and commit", "save changes", or after completing implementation tasks. Flag: --push (a.k.a. "commit and push") stages + commits + pushes to remote in one shot.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/duc01226/EasyPlatform --skill commit命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
[Architecture] Use when designing solution architecture across backend, frontend, deployment, monitoring, testing, and code quality.
[Utilities] Use when you need to answer technical and architectural questions.
[Content] Use when you need to brainstorm as a PO/BA — structured ideation for problem-solving, new product creation, or feature enhancement.
正在显示 SKILL.md
基于 SOC 职业分类
| name | commit |
| version | 2.0.0 |
| description | [Git] Use when asked to "commit", "stage and commit", "save changes", or after completing implementation tasks. Flag: --push (a.k.a. "commit and push") stages + commits + pushes to remote in one shot. |
Goal: Stage changes and create well-structured git commits following Conventional Commits format.
Workflow:
Key Rules:
git log/git blame understands the change without opening the diff. As detailed as the change needs (wrap ~72 chars); no title-only commits for non-trivial changes--push / says "commit and push" → stage + commit + push via git-manager)--amend or unless explicitly requested--no-verifyGenerated with [Claude Code] attribution footerBe skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).
Stage changes and create well-structured git commits following Conventional Commits format.
Before running any git add or git commit commands, create the marker file to bypass the git-commit-block hook:
PROJ=$(git rev-parse --show-toplevel) && mkdir -p "$PROJ/tmp/claude-temp" && touch "$PROJ/tmp/claude-temp/.commit-skill-active"
After committing (success or failure), always clean up the marker:
rm -f "$(git rev-parse --show-toplevel)/tmp/claude-temp/.commit-skill-active"
# Check current status (never use -uall flag)
git status
# See staged changes
git diff --cached
# See unstaged changes
git diff
# Check recent commit style
git log --oneline -5
# Stage all changes
git add .
# Or stage specific files
git add <file-path>
Before committing, check if staged files impact documentation:
git diff --name-only --cached to list staged filesdocs/project-config.json):
docs/specs/.claude/skills/** → may impact .claude/docs/skills/.claude/hooks/** → may impact .claude/docs/hooks/.claude/workflows.json → may impact CLAUDE.md workflow table/docs-update skill, then re-stage any doc changes with git addAnalyze staged changes and generate message following Conventional Commits:
<type>(<scope>): <subject>
<detailed summary of changes>
| Change Pattern | Type |
|---|---|
| New file/feature | feat |
| Bug fix, error handling | fix |
| Code restructure | refactor |
| Documentation only | docs |
| Tests only | test |
| Dependencies, config | chore |
| Performance improvement | perf |
| Formatting only | style |
Extract from file paths:
{configured-source-root}/auth/ → auth.claude/skills/ → claude-skillslibs/{shared-lib}/ → {shared-lib}Body is the deliverable. Optimize for the next person running
git log/git blame— they understand the change without opening the diff. As detailed as the change needs; no artificial brevity limit — wrap ~72 chars, stop once nothing new said. Title-only commit FORBIDDEN for any non-trivial change. — why: the diff shows WHAT; the body must carry WHY + HOW, which the diff cannot.
Structure body in three parts (omit a part only when genuinely empty):
Teach-the-reader mindset (from the
understandskill): cover BOTH high-level motivation (why it matters) AND low-level logic (business rules, edge cases). Surface what a reader would NOT guess from the diff — write the explanation you would want to receive.
Detail dial — scale body to the change:
| Change size | Body depth |
|---|---|
| Trivial (typo, rename, formatting) | Purpose line + 1 bullet; skip "how it works" |
| Normal (feature/fix, single area) | Purpose + 2–5 "what" bullets + a short "how it works" |
| Complex (cross-cutting, subtle bug) | Purpose + grouped "what" + a full "how it works" that spells out the key invariant / edge case / why-this-over-that |
Use HEREDOC for proper formatting:
git commit -m "$(cat <<'EOF'
type(scope): subject
- summarize key change 1 with intent
- summarize key change 2 with impact
Generated by AI
EOF
)"
git status
git log -1
feat(order): add warehouse filter to list
- add warehouse query parameter in order list endpoint
- wire frontend filter control to request payload
- update tests for filtered and unfiltered list behavior
fix(validation): handle empty date range
- guard null/empty date inputs before parsing
- return validation message instead of throwing format exception
git add . (or specific files) so nothing is left behindgit commit --amend unless explicitly requested AND the commit was created in this session AND not yet pushed--no-verify unless explicitly requestedgit log / git blame — surface the non-obvious (key logic, invariants, edge cases, why-this-over-that), not just a list of touched filesGenerated by AIArg --push (a.k.a. "commit and push"): stage all changes + create the commit + push to remote in one shot — spawn git-manager immediately after committing to push. This is the former standalone stage-commit-push entry point folded into commit; it adds no logic beyond the push delegation already described below.
This skill handles commit by default. Push-to-remote and pull request creation are delegated to git-manager sub-agent (subagent_type: "git-manager").
git-manager handles:
--no-verify bypass preventionSpawn git-manager after committing when user says "push", "create PR", or "open PR".
MANDATORY: Push and PR operations spawn
git-managersub-agent (subagent_type: "git-manager"), NOT the main agent. Rationale:git-managerenforces conventional commits, prevents hook bypasses, and handles PR creation with structured summaries.
changelogbranch-comparison[IMPORTANT] Use
TaskCreateto break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ATTENTION ask user whether to skip.
Sub-Agent Selection — Full routing contract:
.claude/skills/shared/sub-agent-selection-guide.mdRule: Route specialized domains (architecture, security, performance, DB, E2E, integration-test, git) to the matching specialist agent (see guide above) — NEVER usecode-reviewerfor these. — why:code-reviewerlacks each domain's checklist, so specialized issues slip through.
AI Mistake Prevention — Failure modes to avoid on every task:
Re-read files after context changes. Context compaction, resume, or long-running work can make memory stale; verify current files before acting. Verify generated content against source evidence. AI hallucinates APIs, names, claims, and document facts. Check the relevant source before documenting or referencing. Check downstream references before deleting or renaming. Removing an artifact can stale docs, generated mirrors, configs, and callers; map references first. Trace the full impact chain after edits. Changing a definition can miss derived outputs and consumers. Follow the affected chain before declaring done. Verify ALL affected outputs, not just the first. One green check is not all green checks; validate every output surface the change can affect. Assume existing values are intentional — ask WHY before changing. Before changing a constant, limit, flag, wording, or pattern, read nearby context and history. Surface ambiguity before acting — don't pick silently. Multiple valid interpretations require an explicit question or stated assumption with risk. Keep shared guidance role-relevant. Universal guidance must help every receiving skill or agent; code-specific obligations belong only in code-specific protocols.
Critical Thinking Mindset — Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence >80% to act. Anti-hallucination: Never present guess as fact — cite sources for every claim, admit uncertainty freely, self-check output for errors, cross-reference independently, stay skeptical of own confidence — certainty without evidence root of all hallucination.
MUST ATTENTION apply critical + sequential thinking — every claim needs appropriate traced evidence (file:line for repo/code claims; source URL or artifact section for research, product, content, and docs claims); confidence >80% to act, <60% DO NOT recommend. Anti-hallucination: never present guess as fact, admit uncertainty freely, cross-reference independently, stay skeptical of own confidence.
MUST ATTENTION apply AI mistake prevention — verify generated content against evidence, trace downstream references before deleting or renaming, verify all affected outputs, re-read files after context loss, and surface ambiguity before acting.
Protocols in force (concise digest of the SYNC/shared blocks this skill carries):
Sub-Agent Selection: route specialized domains to the matching specialist; NEVER code-reviewer.
AI Mistake Prevention: verify generated content against evidence, trace downstream references, verify all affected outputs, re-read after context loss, surface ambiguity.
Critical Thinking: traced file:line proof per claim; confidence >80% to act, never guess.
MANDATORY IMPORTANT MUST ATTENTION break work into small todo tasks using TaskCreate BEFORE starting
MANDATORY IMPORTANT MUST ATTENTION search codebase for 3+ similar patterns before creating new code
MANDATORY IMPORTANT MUST ATTENTION cite file:line evidence for every claim (confidence >80% to act)
MANDATORY IMPORTANT MUST ATTENTION add a final review todo task to verify work quality
[TASK-PLANNING] Before acting, analyze task scope and systematically break it into small todo tasks and sub-tasks using TaskCreate.