一键导入
sqlitecpp-git-branching
SQLiteCpp branch naming and creation rules for starting tasks, issues, or features.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
SQLiteCpp branch naming and creation rules for starting tasks, issues, or features.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
| name | sqlitecpp-git-branching |
| description | SQLiteCpp branch naming and creation rules for starting tasks, issues, or features. |
git status to check current branch.master or wrong branch, create a task-specific branch from master.<issue>-<type>-<short-description>
123-fix-short-description123-feature-short-description<type>-<short-description>
fix-short-descriptionfeature-short-description000- prefix.update-sqlite-X.Y.Z (e.g. update-sqlite-3.52.2).
See [[sqlitecpp-update-sqlite]].release-X.Y.Z. See [[sqlitecpp-release]].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 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.
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.