菜单
Use this skill whenever you author or amend git commits, write a pull request title, or generate suggested commit messages for the javafxTool repository. It enforces the AngularJS Git Commit Message Conventions used by the project.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use this skill whenever you add, upgrade, downgrade or remove a Maven dependency in javafxTool. The project surfaces its bundled dependencies in several places (UI, IDE artifact descriptors, READMEs) and they all have to stay in sync.
Use this skill whenever you change user-facing or developer-facing documentation in javafxTool. The project ships two documentation sites — docsify (`docs/`) and Doxygen (`doxygen/`) — and three README languages, all of which usually need to be updated together.
Use this project skill when implementing, testing, or reviewing changes in the javafxTool JavaFX/Maven codebase.
基于 SOC 职业分类
| name | commit-conventions |
| description | Use this skill whenever you author or amend git commits, write a pull request title, or generate suggested commit messages for the javafxTool repository. It enforces the AngularJS Git Commit Message Conventions used by the project. |
| license | MIT |
javafxTool follows the AngularJS Git Commit Message Conventions. Every commit (including merge / squash titles and any commit messages produced by automation) must match this format. PR titles should also use the format, because the PR title is reused for squash-merge commit messages.
<type>(<scope>): <subject>
<body>
<footer>
<type> and <subject> are required. <scope>, <body> and <footer>
are optional but recommended.| Type | Use it for |
|---|---|
feat | A new feature visible to users or downstream modules. |
fix | A bug fix. |
docs | Documentation-only changes (docs/, doxygen/, README*.md, JavaDoc). |
style | Formatting, white-space, missing semicolons — no functional change. |
refactor | Code change that neither fixes a bug nor adds a feature. |
perf | Performance improvement. |
test | Adding or correcting tests. |
chore | Maintenance, project metadata, IDE files, repo housekeeping. |
build | Changes to the build system or external dependencies (Maven, plugins). |
ci | Changes to GitHub Actions workflows, Jenkins files or other CI configuration. |
revert | Reverts a previous commit; body must contain Reverts: <sha>. |
Use the affected module or area name in lowercase. Common scopes:
core, frame, login, common, demo, smc, qe, cg,
docs, doxygen, ci, deps, release.
If the change spans multiple modules, omit the scope rather than inventing a combined one.
<type>(<scope>): <subject>) ≤ 50 characters.fix(login): handle null username on submit beats
fix(login): bug fix.- ) for multiple items.Closes #123, Fixes #123 or Refs #123 (one per line).BREAKING CHANGE: followed by a description and
a migration note.Feature with issue link:
feat(frame): add easter egg SPI registration
- discover EasterEggService implementations via ServiceLoader
- start enabled providers after sample post-processing
- document the contract in docs/develop/Interface.md
Closes #123
Bug fix:
fix(login): trim whitespace before validating username
Closes #456
Documentation-only change:
docs(doxygen): add contribution workflow page
CI change:
ci: pin actions/checkout to v4
Breaking change:
refactor(core)!: rename TemplateLoaderService to TemplateLoaderProvider
BREAKING CHANGE: implementations must rename their service file under
META-INF/services and update `provides ... with ...` declarations in
module-info.java.
^(feat|fix|docs|style|refactor|perf|test|chore|revert|build|ci)(\([a-z0-9,\-]+\))?!?: .+$.Closes #N syntax.Branch names use a different convention but are tightly coupled to commit practice:
feature/<short-name> for new featuresfix/<short-name> for bug fixesdocs/<scope> for documentation-only branchesNever push commits or open PRs from master.