// OhMyCode commit message conventions. MUST load on every git commit — provides Conventional Commits format with scope inference from file paths.
| name | commit-conventions |
| description | OhMyCode commit message conventions. MUST load on every git commit — provides Conventional Commits format with scope inference from file paths. |
<type>(<scope>): <description>
All lowercase. Description should be imperative mood ("add", not "adds" or "added").
| Type | When to Use |
|---|---|
feat | New feature or capability |
fix | Bug fix |
docs | Documentation only |
test | Adding or updating tests |
refactor | Code change that neither fixes a bug nor adds a feature |
chore | Build, tooling, dependency changes |
style | Formatting, whitespace (no logic change) |
Infer scope from the primary file path changed:
| Path Pattern | Scope |
|---|---|
ohmycode/tools/* | tools |
ohmycode/core/* | core |
ohmycode/providers/* | providers |
ohmycode/config/* | config |
ohmycode/memory/* | memory |
ohmycode/storage/* | storage |
ohmycode/cli.py | cli |
tests/* | same as the source being tested |
docs/* | omit scope |
.claude/skills/* or .agents/skills/* | skills |
If changes span multiple scopes, use the primary one or omit scope.
feat(tools): add sql_query tool
fix(providers): handle empty delta in OpenAI streaming
docs: update DEVELOPMENT_GUIDE with hook system
test(core): add permission rule matching edge cases
refactor(cli): extract render_stream into separate module
chore: bump openai dependency to 1.52.0
feat(skills): add debug-ohmycode skill
fix(core): handle empty messages (#42)! after scope: feat(config)!: change rules formatRun OhMyCode benchmarks — score any provider/model with token tracking. Use when user wants to benchmark, evaluate, test performance, or compare models.
Generate high-quality tests for OhMyCode modules. Use when user wants to create, add, or generate tests for a module or file.
Run tests and analyze results for OhMyCode. Use when user wants to run, check, or verify tests — or after any code change.
Guide for debugging OhMyCode issues. Use when user reports errors, unexpected behavior, or connection problems.
Guide for adding a new feature to OhMyCode. Use when user wants to add functionality that goes beyond existing extension points (tools/providers). Always start by reading docs/DEVELOPMENT_GUIDE.md.
Guide for adding a new LLM provider to OhMyCode. Use when user wants to connect a new AI model backend.