菜单
Guide for creating well-structured conventional commits. Use when creating git commits, drafting commit messages, or reviewing commit message quality.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/code0100fun/botfiles --skill commit-message-guide命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | commit-message-guide |
| description | Guide for creating well-structured conventional commits. Use when creating git commits, drafting commit messages, or reviewing commit message quality. |
This skill ensures commit messages follow conventional commit format with command tense and concise, meaningful content.
<type>(<scope>): <subject>
[optional body]
[optional footer]
Use one of these conventional commit types:
feat: New featurefix: Bug fixrefactor: Code change that neither fixes a bug nor adds a featureperf: Performance improvementstyle: Code style changes (formatting, missing semicolons, etc.)test: Adding or updating testsdocs: Documentation changesbuild: Build system or dependency changesci: CI/CD configuration changeschore: Other changes that don't modify src or test filesThe scope provides context about what area of the codebase is affected. Use appropriate scope for the module/component being changed, e.g.:
api, auth, db, ui, config, cli, coreExamples:
feat(api): add support for batch operationsfix(auth): handle expired token refreshrefactor(db): simplify query builder logicBad examples:
feat(api): Added support for batch operations (wrong tense)Fixed a bug in auth (missing type/scope, wrong tense)Only include a body when the title and file changes alone cannot reasonably convey the reason for the commit.
feat(api): add support for webhook callbacks
Implements webhook delivery for event notifications.
Uses a retry queue with exponential backoff to handle
transient failures without losing events.
refactor(db): restructure query parser
Reorganizes query parsing to use a table-driven approach
instead of a large switch statement. This makes it easier
to add new query types and reduces code duplication.
fix(auth): correct token expiry handling
Changes 3 files with 45 additions and 12 deletions.
All tests pass.
This fix took longer than expected, about 2 days.
WIP: debugging race condition in scheduler
These don't need to follow strict formatting and may have failing tests.
fixup! feat(api): add support for webhook callbacks
Created with git commit --fixup=<commit-hash> for automatic squashing during rebase.
Before creating a commit, verify:
Exception: WIP or FIXUP commits may skip these requirements.
feat(ui): add variable binding display command
The title clearly describes what was added. The diff will show the implementation.
perf(core): optimize instruction dispatch loop
Replace computed goto with direct threaded code. This
reduces dispatch overhead by eliminating one memory
indirection per instruction. Trade-off is slightly
larger binary size due to code duplication.
fix(db): handle empty name table
Modified src/db.zig to add a check for empty tables.
Updated tests to cover this edge case. All 47 tests pass.
This was a quick fix, only took about an hour.
None of this information adds value.
Guide for using bees, a local-first issue tracker (SQLite DB + a committed issues.jsonl) driven by the `bees` CLI. Use for ALL task/issue tracking on bees projects — creating issues, organizing them into epics with dependencies, the in_progress→closed lifecycle, and syncing/committing the tracker.
My personal cross-codebase development workflow — set up tooling with mise, track work in Bees, make focused changes, commit with the commit-message-guide conventions, and land the plane cleanly. Use when starting or running a development task on a project that follows this workflow (mise + Bees + Git).
Guide for using mise (mise-en-place) — the polyglot tool-version manager, task runner, and environment manager configured via mise.toml. Use when a project has a mise.toml/.mise.toml, when installing or pinning tool versions, running project tasks (mise run / mise exec), or setting up a reproducible dev environment.