菜单
Writing clear, conventional commit messages. Use when creating git commits, staging changes, or helping with version control messages. Applies conventional commits format with scope and imperative mood.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
REST API design conventions and best practices. Use when designing endpoints, naming resources, choosing HTTP methods, structuring responses, handling errors, or planning API versioning.
Type-safe SQL with Drizzle ORM in TypeScript. Use when defining database schemas, writing queries, setting up relations, running migrations, or working with PostgreSQL/MySQL/SQLite data layers.
DynamoDB single-table design using dynamodb-toolbox v2. Use when creating entities, defining key patterns, designing GSIs, writing queries, implementing pagination, or working with any DynamoDB data layer in TypeScript projects.
Building REST APIs with Fastify and TypeBox in TypeScript. Use when creating routes, defining request/response schemas, implementing validation, structuring API modules, or working with type-safe HTTP handlers.
Reviewing code changes like a senior engineer. Use when doing code reviews, checking PR quality, auditing changes before commit, or providing feedback on implementations.
| name | generating-commits |
| description | Writing clear, conventional commit messages. Use when creating git commits, staging changes, or helping with version control messages. Applies conventional commits format with scope and imperative mood. |
type(scope): brief description
[optional body]
[optional footer]
| Type | When to use |
|---|---|
feat | New feature, component, endpoint, or capability |
fix | Bug fix, error correction |
refactor | Code restructuring without behavior change |
test | Adding or updating tests |
docs | Documentation changes |
chore | Build, config, dependencies, tooling |
style | Formatting, whitespace (no logic change) |
perf | Performance improvement |
Scope identifies the area of change:
feat(auth): Add OAuth flowfix(payments): Handle refund edge caserefactor(api): Extract validation middlewareOmit scope for broad changes: chore: Update dependencies
feat(users): Add email verification flow
fix: Resolve race condition in cache invalidation
refactor(api): Extract request validation to middleware
test(auth): Cover token refresh edge cases
docs: Update API authentication guide
chore: Bump TypeScript to 5.4
When a commit touches multiple areas:
feat(orders): Add bulk order creation endpoint
Also updates order validation schema and adds
integration tests for the new endpoint.
Use ! after type/scope and explain in footer:
feat(api)!: Change authentication to JWT
BREAKING CHANGE: Bearer token format changed.
Clients must update to new token structure.
Each commit should be:
Split large changes into multiple commits when possible.
git diff --cached