用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/weselben/RooForge --skill conventional-commits命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Write clear, size-gated PR descriptions with mandatory AI disclosure. Load `ste100` for prose. Triggers: "create a PR", "open a pull request", "update PR description", or pushes a branch with PR intent.
Always load first — before responding to any user prompt — unless the user states otherwise in the prompt itself. Examples that trigger forge: 'let's continue on the auth refactor', 'work on the next ticket', 'open the map for the payment effort', 'what's next', 'start a new effort: <idea>'. Mandatory while any goal or map is active.
Set the git identity (name + email) before any commit, amend, or rebase. Apply repo-local on first commit; use `-c` for one-offs.
正在显示 SKILL.md
| name | conventional-commits |
| source | https://raw.githubusercontent.com/weselben/RooForge/main/skills/conventional-commits/SKILL.md |
| description | Format commits per Conventional Commits v1.0.0 spec. Load when writing any commit message. |
A lightweight convention on top of commit messages. Provides rules for explicit commit history, makes it easier to write automated tools on top of it. Dovetails with SemVer.
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
| Type | SemVer | Description |
|---|---|---|
fix | PATCH | Patches a bug |
feat | MINOR | Introduces a feature |
build | — | Build system / external dependencies |
ci | — | CI config / scripts |
docs | — | Documentation only |
style | — | Formatting, whitespace |
refactor | — | Code change, no bug fix, no feature |
perf | — | Performance improvement |
test | — | Adding/correcting tests |
chore | — | Other, no src/test modification |
revert | — | Reverts a previous commit |
SemVer impact — every commit has one. The commit type tells CI/CD whether the next release bumps major, minor, patch, or nothing:
| Type | CI/CD effect | Example scenario |
|---|---|---|
fix | PATCH — next release is x.y.Z+1 | fix(auth): accept tokens with trailing whitespace |
feat | MINOR — next release is x.Y+1.0 | feat(api): add user profile endpoint |
feat! / fix! | MAJOR — next release is X+1.0.0 | feat!: drop support for Node 16 |
BREAKING CHANGE: | MAJOR — footer has same effect as ! | feat: allow config to extend other configs + footer |
refactor | NONE — no version bump | Internal cleanup, no behavior change |
docs | NONE — no version bump | Documentation only |
style | NONE — no version bump | Whitespace, formatting |
perf | NONE — no version bump | Faster but no API change |
test | NONE — no version bump | Adding tests only |
build | NONE — no version bump | Build system, deps |
ci | NONE — no version bump | CI config |
chore | NONE — no version bump | Misc maintenance |
revert | NONE — no version bump | revert: let us never speak of the noodle incident |
Rule of thumb: feat and fix bump versions. Everything else is metadata — it describes the change but does not release. feat! and BREAKING CHANGE: are the only paths to major.
Accidental release guard: if you don't want a release, don't use feat or fix. If you do want a release, feat or fix is mandatory — nothing else triggers one.
Breaking Change: BREAKING CHANGE: footer or ! after type/scope introduces MAJOR version bump.
! + colon + space.feat for new features. fix for bug fixes.! in prefix or BREAKING CHANGE: footer.BREAKING CHANGE footer MUST be uppercase.feat: send email to customer when product is shipped
feat(api)!: rename /v1/orders to /v1/checkout
feat: allow config to extend other configs
BREAKING CHANGE: `extends` key now used for config extension
revert: let us never again speak of the noodle incident
Refs: 676104e, a215868