518b8eca85
md-first memory extraction framework for AI agents. Markdown is the single source of truth; SQLite holds state and LanceDB provides the rebuildable vector + BM25 + scalar index. The codebase follows a single-direction DDD layering (entrypoints -> service -> memory -> infra, with component / core / config cross-cutting) enforced by import-linter. Engineering surface: - Coding conventions in .claude/rules/ (path-scoped) and workflows in .claude/skills/ (/commit, /new-branch, /pr). - GitHub Actions CI runs make lint + test + integration; pre-commit mirrors the gates locally (ruff, hygiene hooks, gitlint commit-msg). - Commit messages follow Conventional Commits, enforced by gitlint. - make lint also enforces datetime two-zone discipline and OpenAPI drift.
44 lines
1.2 KiB
Markdown
44 lines
1.2 KiB
Markdown
---
|
|
name: new-branch
|
|
description: Create a branch following the project's GitFlow Lite model
|
|
---
|
|
|
|
# /new-branch
|
|
|
|
Cut a new branch under the GitFlow Lite model.
|
|
|
|
## Branch model
|
|
|
|
```
|
|
master = released / stable (tagged on release; protected)
|
|
dev = integration branch (protected)
|
|
feat/* = cut from dev → PR → merge into dev
|
|
fix/* = cut from dev → PR → merge into dev
|
|
hotfix/* = cut from master → merge into master AND synced into dev (double merge)
|
|
release = dev → master + tag on master (no separate release branch)
|
|
```
|
|
|
|
## Steps
|
|
|
|
1. Ask (or infer) the change type: `feat`, `fix`, or `hotfix`.
|
|
2. Pick the parent:
|
|
- `feat/*`, `fix/*` → branch from **`dev`**.
|
|
- `hotfix/*` → branch from **`master`**.
|
|
3. Update the parent first:
|
|
```bash
|
|
git checkout <parent>
|
|
git pull --ff-only
|
|
```
|
|
4. Create the branch with a kebab-case slug:
|
|
```bash
|
|
git checkout -b feat/<short-slug>
|
|
```
|
|
5. For a `hotfix`, remember it must later merge into **both** `master` and `dev`.
|
|
|
|
## Naming
|
|
|
|
- `feat/add-agentic-rerank`, `fix/empty-profile-crash`, `hotfix/lancedb-conn-leak`.
|
|
- Lowercase, hyphen-separated, no spaces, concise.
|
|
|
|
Never commit directly to `master` or `dev` — always via a branch + PR.
|