菜单
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).
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/code0100fun/botfiles --skill dev-workflow命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
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.
Guide for creating well-structured conventional commits. Use when creating git commits, drafting commit messages, or reviewing commit message quality.
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.
| name | dev-workflow |
| description | 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). |
My default way of working on almost any codebase. It composes three companion skills — mise, bees-issue-tracker, and commit-message-guide — which install automatically as dependencies of this plugin. This skill orchestrates them; it does not restate them.
Use the mise skill. After cloning, run mise install (and mise trust if prompted) to get the pinned tool versions. Discover the project's commands with mise tasks and run everything through mise run <task> rather than raw invocations.
Use the bees-issue-tracker skill. Start with bees prime. Create an issue before non-trivial work, and set it in_progress when you actually start — keep one issue in_progress at a time.
Work in small, verifiable increments. Run the project's checks via mise tasks (mise run test, mise run lint) as you go — don't let a change pile up unverified.
Use the commit-message-guide skill to draft the message (type(scope): subject, imperative mood, a body only when it adds value, no AI attribution). Stage specific files. Keep code commits separate from tracker commits. Do not git commit or git push automatically — only when I ask.
Wrap up so the next session has full context:
bees close <id> --reason "…" for finished work (or add progress notes to in_progress items), then bees sync and commit the .bees/issues.jsonl change — separately from code.in_progress at a time — the tracker should always reflect what's actively being worked.mise run <task> over remembering raw commands.