docs: add git commit convention to AGENTS.md
This commit is contained in:
parent
bcb5465247
commit
6930858074
5
.opencode/svelte.json
Normal file
5
.opencode/svelte.json
Normal file
@ -0,0 +1,5 @@
|
||||
{
|
||||
"mcp": {
|
||||
"type": "local"
|
||||
}
|
||||
}
|
||||
10
AGENTS.md
10
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**: `<type>[optional scope]: <description>`
|
||||
- **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
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user