菜单
SQLiteCpp change workflow checklists for API, tests, build files, and CHANGELOG updates. Use when adding a method or class, editing build files, or writing a CHANGELOG entry for a PR.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | sqlitecpp-workflow |
| description | SQLiteCpp change workflow checklists for API, tests, build files, and CHANGELOG updates. Use when adding a method or class, editing build files, or writing a CHANGELOG entry for a PR. |
@brief, @param, @return, @throw).tests/.CMakeLists.txt, meson.build).CHANGELOG.md updated for user-facing changes.Update CHANGELOG.md in the same PR that makes the change, not in a later batch. Add one line per
PR under the current unreleased version heading (Version X.Y.Z - <year> ???). Create that heading
if it does not exist yet.
- <description> (#NNN). The PR number is the last token, in parentheses.(#NNN) and note
it was committed directly to master.humanizer skill before committing so the
prose stays plain and free of AI tells.Finalizing the version heading and tagging belong to the release process: see [[sqlitecpp-release]].
gh pr create against master.humanizer if unsure.include/SQLiteCpp/<Class>.h with Doxygen.src/<Class>.cpp.tests/<Class>_test.cpp.CHANGELOG.md.include/SQLiteCpp/NewClass.h and src/NewClass.cpp.CMakeLists.txt (SQLITECPP_SRC and SQLITECPP_INC).meson.build.SQLiteCpp.h if public API.tests/NewClass_test.cpp.CMakeLists.txt and meson.build.SQLiteCpp CI workflow patterns. Use for GitHub Actions, AppVeyor, Travis, matrices, or test steps.
Running shell commands on this Windows checkout via the PowerShell and Bash tools, and passing multi-line or quoted arguments (commit messages, PR bodies, file content) without corruption. Use when running git or gh with multi-line or quoted input, writing a commit message or PR body from the command line, reaching for a heredoc or here-string, or after a message or body comes out wrapped in stray characters such as a leading and trailing `@`.
SQLiteCpp coding standards and API rules for core edits, public headers, style, and Doxygen.
Default response behavior for AI coding agents: professional, factual, neutral tone with calibrated critical evaluation. Baseline for every task: implementation, code review, debugging, planning, research, evaluation, Q&A.
Editing conventions for files under `.claude/skills/**` (markdown style, frontmatter format, SKILL.md vs `references/` split, upstream-vendored skills). Use when creating a new skill, editing any `SKILL.md` or `references/*.md` file, refactoring a skill description, or after adding/removing a skill.
SQLiteCpp branch naming and creation rules for starting tasks, issues, or features.