Emma ThorpeandClaude Opus 4.8
a97b433a7b
Vendor the auto-memory directory into the repo (claude/memory/) and symlink it read-only into ~/.claude/memory. Recall keeps working; the runtime "save a memory" path no longer writes there. CLAUDE.md instructs Claude to add/change memories in this repo and rebuild instead, so the flake stays the single source of truth. README documents the split. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.3 KiB
name, description, metadata
| name | description | metadata | ||||||
|---|---|---|---|---|---|---|---|---|
| git-conventions | Branch naming and commit message conventions for git workflow |
|
Never commit directly to the default branch (main/master). Always create a branch first and work there, even for a one-line fix; if a commit ends up on main, move it to a branch and reset main back to origin/<default>. This is a hard rule.
Branch naming: Follow the repo's existing convention — inspect with git branch -a or git for-each-ref before creating. Prefer Conventional Commits prefixes (feat/, fix/, chore/, docs/, refactor/). Format: <prefix>/<TICKET-ID>-<kebab-summary>. Only ask if no convention is discoverable.
Commit messages: Conventional Commits. Subject line: <type>(<TICKET-ID>): <imperative summary> — ticket ID as the scope. Use additional -m flags for rationale/body. Commit at logical checkpoints, not one giant final commit.
Why: Lyra's standard workflow for traceability and clean history.
How to apply: Whenever creating a branch or committing in any repo. Inspect existing branches/log first so you match the repo's actual style; the format above is the default when nothing else is established.