菜单
Write commit messages, changelogs, release notes, and manage versioning following Conventional Commits with required scope. Use when the user asks for a commit message, changelog, release notes, versioning, tagging, or how to format commits.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/micaelmalta/agentic --skill git-commits命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | git-commits |
| description | Write commit messages, changelogs, release notes, and manage versioning following Conventional Commits with required scope. Use when the user asks for a commit message, changelog, release notes, versioning, tagging, or how to format commits. |
| triggers | ["/commit","commit message","write commit message","changelog","release notes","conventional commits","format my commit","version bump","create release","tag release","semantic versioning"] |
"Commits tell a story; changelogs tell users what changed."
Write clear, consistent commit messages and changelogs so history is readable and releases are understandable.
Follow Conventional Commits when the project does not specify otherwise:
<type>(<scope>): <short summary>
[optional body]
[optional footer(s)]
Format Rules:
<type>: Required, lowercase type from list below(<scope>): Required, noun describing section of codebase (e.g., api, auth, ui, db)<short summary>: Required, imperative mood, lowercase, no period, ~72 chars max! after scope: feat(api)!: drop support for Node 12Scope Naming:
api, not API)auth not login-form-button)api, auth, ui, db, cli, docs, config, deps, tests, ci, builduser-service, payment-flow, dashboardoauth, search, notificationsgit log --oneline for existing patterns)Types: feat, fix, docs, style, refactor, test, chore, perf, ci, build, revert.
Breaking Changes:
! after scope: refactor(api)!: drop deprecated endpointsBREAKING CHANGE: description of what brokeBody: Use when you need to explain "why", context, or side effects. Leave blank line after summary.
Footers: BREAKING CHANGE: <description>, Fixes #123, Closes #456, Refs #789
Examples:
feat(auth): add OAuth2 social login
fix(api): prevent race condition in user creation
docs(readme): update installation instructions
refactor(db)!: migrate from MySQL to PostgreSQL
BREAKING CHANGE: Database schema incompatible with v1.x
chore(deps): upgrade TypeScript to v5
test(api): add integration tests for user endpoints
perf(search): optimize query with database index
CHANGELOG style).Use SemVer (MAJOR.MINOR.PATCH): MAJOR for breaking changes, MINOR for new features, PATCH for bug fixes.
For complete versioning guide: See reference/VERSIONING.md, which covers:
Create annotated tags (git tag -a v1.2.3 -m "Release v1.2.3") with v prefix. Use automated tools (semantic-release, release-please) or manual workflow (update version, CHANGELOG, commit, tag, push).
For complete release guide: See reference/RELEASES.md, which covers:
Project Conventions:
feat(api): PROJ-123 add endpoint), include themReference: Conventional Commits
! after scope or BREAKING CHANGE: footerBREAKING CHANGE:, Fixes #123, Closes #456git tag -a)| Situation | Skill to invoke | How |
|---|---|---|
| Need to version based on commit history | Use SemVer rules in Section 4 above | Automated: semantic-release / release-please |
| Commit includes security fix | security-reviewer skill | Read skills/security-reviewer/SKILL.md to verify fix |
| Commit includes breaking API change | architect / documentation skill | Update API docs and write ADR |
| Revert commit needed | Use git revert <SHA> | Creates new commit that undoes changes (safe; don't use git reset) |
See also: ci-cd skill for automating releases in CI/CD pipelines.
Complete development workflow from planning to GitHub PR using PARA methodology and RLM for large codebases. Use when implementing a feature, fixing a bug, refactoring, or taking work from plan to GitHub PR.
Analyze and improve performance: profile, find bottlenecks, optimize, and instrument code with observability for diagnosing performance issues (profiling, bottleneck tracing). Use when the user asks about performance, slow code, bottlenecks, profiling, optimization, or adding performance-specific observability.
Design and implement tests (unit, integration, e2e, accessibility, i18n), improve coverage, and run test suites. Use when the user asks to add tests, write tests, improve coverage, run tests, test accessibility, test translations, or implement test strategy.