# Sqlitecpp Git Branching

> SQLiteCpp branch naming and creation rules for starting tasks, issues, or features.

- Skill: `srombauts/sqlitecpp-git-branching` (Agent Skill)
- Install (CLI): `npx skillmds@latest add srombauts/sqlitecpp-git-branching`
- Raw SKILL.md: https://api.skillmd.com/api/skills/srombauts/sqlitecpp-git-branching/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: srombauts (https://skillmd.com/u/srombauts)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/srombauts/sqlitecpp-git-branching

---


# SQLiteCpp Git Branching

## When to create a branch
- User mentions working on a task, issue, or feature.
- User references a GitHub issue number.

## Before starting work
1. Run `git status` to check current branch.
2. If on `master` or wrong branch, create a task-specific branch from `master`.

Create the branch before the first edit. If edits were accidentally made on `master`, create the task
branch with the working tree intact before continuing.

## Branch naming
- With issue: `<issue>-<type>-<short-description>`
  - `123-fix-short-description`
  - `123-feature-short-description`
- Without issue: `<type>-<short-description>`
  - `fix-short-description`
  - `feature-short-description`
- Issue ID is optional; do not use a `000-` prefix.

## Maintenance branch conventions
- Updating the bundled SQLite3: `update-sqlite-X.Y.Z` (e.g. `update-sqlite-3.52.2`).
  See [[sqlitecpp-update-sqlite]].
- Cutting a release: `release-X.Y.Z`. See [[sqlitecpp-release]].

## Branch-only requests
- If the user only requests a branch, create it and stop (no file changes).