From 69308580745ac96ecb357c6e53ed4021239b2bcd Mon Sep 17 00:00:00 2001 From: "Veit F." Date: Sun, 17 May 2026 17:29:53 +0200 Subject: [PATCH] docs: add git commit convention to AGENTS.md --- .opencode/svelte.json | 5 +++++ AGENTS.md | 10 ++++++++++ 2 files changed, 15 insertions(+) create mode 100644 .opencode/svelte.json diff --git a/.opencode/svelte.json b/.opencode/svelte.json new file mode 100644 index 0000000..574943d --- /dev/null +++ b/.opencode/svelte.json @@ -0,0 +1,5 @@ +{ + "mcp": { + "type": "local" + } +} diff --git a/AGENTS.md b/AGENTS.md index ea0999e..10d1a7d 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -35,3 +35,13 @@ When working through OpenSpec artifacts (`/opsx-*` commands), apply the same Sve ### Skills Load `svelte-core-bestpractices` skill when writing or reviewing Svelte components. Load `svelte-code-writer` skill for CLI-based documentation lookups and code analysis. + +## Git Commit Convention + +All git commits must follow [Google's conventional commit message format](https://github.com/googleapis/google-claude/blob/main/docs/completion-conventions.md): + +- **Subject line**: Maximum 50 characters, imperative mood, no period at the end +- **Format**: `[optional scope]: ` +- **Allowed types**: `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `build`, `ci`, `chore`, `perf` +- **Body** (if needed): Blank line after subject, then detailed explanation wrapped at 72 characters +- **Footer** (if needed): Use for breaking changes (`BREAKING CHANGE: ...`) and issue references