菜单
Use when creating git commits, writing commit messages, or when about to run git commit -- enforces structured commit message format with imperative mood, capitalized subjects, 72-char wrapping
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill whenever implementing type, field, or schema changes across the duc monorepo. Triggers when the user asks to add a new field, change a type, rename a property, or propagate any data model change across the duc codebase. Also triggers when the user mentions duc.sql, schema migrations, DataState, or any of the cross-language duc type files (ducrs, ducjs, ducpy). Always use this skill before touching duc type files — it tells you exactly which files to edit and in what order.
Retrieves up-to-date documentation, API references, and code examples for any developer technology. Use this skill whenever the user asks about Context7 or a specific library, framework, SDK, CLI tool, or cloud service — even for well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot. Your training data may not reflect recent API changes or version updates. Always use for: API syntax questions, configuration options, version migration issues, "how do I" questions mentioning a library name, debugging that involves library-specific behavior, setup instructions, and CLI tool usage. Use even when you think you know the answer — do not rely on training data for API details, signatures, or configuration options as they are frequently outdated. Always verify against current docs. Prefer this over web search for library documentation and API details.
Generates technical guides that teach real-world use cases through progressive examples. **Auto-activation:** User asks to write, create, or draft a guide or tutorial. Also use when converting feature documentation, API references, or skill knowledge into step-by-step learning content. **Input sources:** API documentation, existing code examples, or user-provided specifications.
| name | commit-messages |
| description | Use when creating git commits, writing commit messages, or when about to run git commit -- enforces structured commit message format with imperative mood, capitalized subjects, 72-char wrapping |
| license | MIT |
Every commit message follows a consistent format. The subject line completes the sentence: "If applied, this commit will <your subject line>". When present, the body explains why, not what.
The project uses Conventional Commits with type-prefixed body lines. Type and scope are lowercase; the description after the colon is capitalized and imperative.
Follow existing instructions for commits if present in the repository. Check git log --oneline -20 to see recent patterns and match the existing style.
Project convention always wins. The rules below are the default when no convention is detected.
fix:, feat:, refactor:, style:, perf:, docs:, chore:).
feat: if the commit introduces a new feature or functionality.fix: resolve layout reactivity and extract version history tool.feat(canvas): or fix(backend):.fix:, feat:, refactor:, style:, etc.Consider the following references when creating new commit messages: