SerpentStack git-workflow

Git conventions for this project. Use when: creating branches, writing commit messages, opening PRs, or running the pre-push checklist.

install

source · Clone the upstream repo

git clone https://github.com/Benja-Pauls/SerpentStack

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/Benja-Pauls/SerpentStack "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.skills/git-workflow" ~/.claude/skills/benja-pauls-serpentstack-git-workflow && rm -rf "$T"

manifest: .skills/git-workflow/SKILL.md

source content

Git Workflow

Branch Naming

Use prefixed branch names:

```
feature/short-description
```
— new functionality
```
fix/short-description
```
— bug fixes
```
chore/short-description
```
— tooling, dependencies, config
```
refactor/short-description
```
— code restructuring

Lowercase, hyphens, under 50 characters.

Commit Messages

Follow Conventional Commits:

<type>: <short summary under 72 chars>

Types:

feat

fix

chore

docs

test

refactor

style

Pull Request Format

gh pr create \
  --title "feat: add projects endpoint" \
  --body "## Summary
- What changed and why (1-3 bullets)

## Test plan
- How the changes were verified"

Pre-Push Checklist

Before pushing, run the full verification suite:

make verify   # lint + typecheck + test for both backend and frontend

This runs the same checks as CI, so if it passes locally, CI will pass too.