菜单
Formats Git commit messages following Conventional Commits conventions. Use when the user asks to commit, write a commit message, format commits, or mentions conventional commits, staged changes, or release notes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Checks components and pages for WCAG 2.1 accessibility violations. Use when the user asks about a11y, WCAG compliance, screen readers, aria labels, keyboard navigation, or accessible patterns.
Creates platform-specific ad copy for paid campaigns with A/B variants. Use when the user asks about ad copy, PPC ads, Google Ads, Facebook ads, LinkedIn ads, or paid campaign copy.
Generates TypeScript interfaces from API responses or OpenAPI schemas. Use when the user asks about typing API responses, creating interfaces from JSON, parsing Swagger/OpenAPI, or keeping types in sync with backend.
Creates structured blog post outlines based on topics and keywords. Use when the user asks about blog structure, content outlines, SEO article planning, or wants to organize ideas before writing.
Template skill providing the single source of truth for brand guidelines, design tokens, technology choices, and voice/tone. Customize this template for your brand. Use when generating UI components, styling applications, writing copy, or creating user-facing assets to ensure brand consistency.
Creates comprehensive brand voice and tone documentation with messaging pillars, vocabulary guidelines, and writing examples. Use when the user asks about brand voice, tone guides, writing style, brand personality, or messaging consistency.
| name | formatting-commit-messages |
| description | Formats Git commit messages following Conventional Commits conventions. Use when the user asks to commit, write a commit message, format commits, or mentions conventional commits, staged changes, or release notes. |
git diff --cached<type>[optional scope][!]: <description>
[optional body]
[optional footer(s)]
| Type | When to Use |
|---|---|
feat | New feature for the user |
fix | Bug fix for the user |
docs | Documentation only changes |
style | Formatting, missing semicolons (no code change) |
refactor | Code change that neither fixes nor adds feature |
perf | Performance improvement |
test | Adding or correcting tests |
build | Changes to build system or dependencies |
ci | CI configuration changes |
chore | Other changes that don't modify src or tests |
revert | Reverts a previous commit |
! after type/scope: feat(api)!: remove deprecated endpointsBREAKING CHANGE: footer in the bodyRun the following to get staged diffs:
git diff --cached --stat
git diff --cached
Analyze the changes to determine the appropriate type:
src/ with new functionality → featfix*.md, *.txt, or docs folder → docsstylerefactorperftestpackage.json, webpack.config.*, tsconfig.* → build.github/workflows/, CI configs → cichoreDerive scope from the primary affected area:
src/components/Button.tsx → scope: buttonsrc/api/users.ts → scope: api or userslib/utils/ → scope: utilsLook for indicators of breaking changes:
Subject line rules:
Body (if needed):
Footer (if needed):
BREAKING CHANGE: <description>Fixes #123 or Closes #456Reviewed-by: Name <email>Present the formatted message to the user:
**Suggested commit message:**
feat(auth): add OAuth2 login support
Implement OAuth2 authentication flow with Google and GitHub providers.
Users can now sign in using their existing accounts.
Closes #142
If approved, execute:
git commit -m "<subject>" -m "<body>" -m "<footer>"
Or for simple commits:
git commit -m "<type>(<scope>): <description>"
feat(cart): add quantity selector to cart items
fix(auth): prevent token refresh race condition
Multiple simultaneous requests could trigger parallel refresh attempts.
Added mutex lock to ensure single refresh execution.
Fixes #287
feat(api)!: migrate to v2 response format
BREAKING CHANGE: API responses now use camelCase keys instead of snake_case.
All clients must update their parsing logic.
docs(readme): add installation instructions for Windows
refactor(utils): extract date formatting into separate module
Before committing, verify:
git status to confirm. Prompt user to stage files first.git status for conflicts or hooks blocking commit.git commit --help for options.