From ea1e8a19abe7cd0786f98ee23fd0c55c42ac1a31 Mon Sep 17 00:00:00 2001 From: Ben Allfree Date: Wed, 22 Apr 2026 04:52:44 -0700 Subject: [PATCH] chore: add commit message convention guidelines for monorepo --- .cursor/rules/commit-message-convention.mdc | 25 +++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 .cursor/rules/commit-message-convention.mdc diff --git a/.cursor/rules/commit-message-convention.mdc b/.cursor/rules/commit-message-convention.mdc new file mode 100644 index 0000000..99c0074 --- /dev/null +++ b/.cursor/rules/commit-message-convention.mdc @@ -0,0 +1,25 @@ +--- +description: Monorepo conventional commit message format +alwaysApply: true +--- + +# Commit Message Convention + +Use monorepo-style conventional commit messages for all git commits. + +## Format + +`type(scope): subject` + +- `type` is a conventional commit type like `feat`, `fix`, `chore`, `docs`, `refactor`, or `test`. +- `scope` should identify the monorepo package or area (for example `lotato`, `lo-star`, `meshtastic`). +- `subject` must be concise, imperative, and lowercase when possible. + +## Limits + +- Keep the full commit subject line to **50 characters or fewer**. + +## Examples + +- `feat(lotato): add meshcore cli gateway` +- `fix(lo-star): correct readme typo`