This repo documents our lab's code management conventions and provides Claude Code skills that enforce them. The conventions describe what to do; the skills automate how to do it.
This lab uses two git workflow strategies depending on the project type:
- Semver Versioned Software — for R/Python packages and libraries with semantic versioning. Uses Gitflow with
main,develop, feature, release, and hotfix branches. - End-User Services — for web apps, mobile apps, and deployed services. Uses trunk-based development off
mainwith feature and hotfix branches.
Choose the workflow that matches your project and reference it in your project's CLAUDE.md.
- Branching Conventions — branch naming patterns per workflow
- Commit Conventions — message format and principles
- Pull Request Conventions — PR titles, descriptions, and lifecycle
- Code Review Practices — two-pass review: AI review then human review
Skills live in .claude/skills/ and can be referenced from any project's CLAUDE.md to enforce these conventions automatically.
| Skill | Command | Applies |
|---|---|---|
| Commit | /commit |
Commit Conventions |
| PR Create | /pr-create |
PR Conventions |
| Branch Review | /branch-review |
Code Review Practices |
Feel free to submit suggestions as issues or PRs.
- Images
- Figures should always be in
.drawio.svgformat. - Figures require using draw.io or (preferred) the "Draw.io Integration" for VSCode.
- Figures should always be in
Please see if your suggestion is in the todo list, or consider adding it to that list if you don't have an implementation yet.