Menu
Commit message and branch naming conventions. Use when writing commit messages, naming branches, or squashing changes before a pull request.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | commits |
| description | Commit message and branch naming conventions. Use when writing commit messages, naming branches, or squashing changes before a pull request. |
| license | Proprietary. See LICENSE for complete terms. |
| metadata | {"author":"kNoAPP","version":"1.2.0"} |
This project uses Conventional Commits.
<type>(<scope>): <short description>
[optional body]
[optional footer]
| Type | When to use |
|---|---|
feat | New feature or capability |
fix | Bug fix |
docs | Documentation only |
style | Formatting-only code changes |
refactor | Code change with no behavior change |
perf | Performance improvement |
test | Adding or updating tests |
build | Build system or external deps |
ci | CI/CD workflow changes |
chore | Dependency updates, tooling, config |
revert | Revert previous changes |
Breaking changes append ! to the type: feat!: drop support for v1 frames.
add wifi reconnect, not Added WiFi Reconnect.fix(parser): handle malformed BLE frames.Per CONTRIBUTING.md, branches follow:
<handle>/<issue#>-<type>-<short-description>
<handle> is your GitHub handle. When there is no linked issue, use none for
<issue#>. Types match the commit types above (feat, fix, docs,
refactor, test, ci, chore).
Examples: kNoAPP/41-feat-wifi-reconnect, mario/none-chore-modify-eslint,
docs/readme-update
Project stack, module layout, and core data flow. Use when navigating the codebase, locating where functionality lives, or understanding how the client, Zustand store, and persistence layers connect.
Workflow for evaluating and resolving pull request review feedback. Use when asked to "resolve feedback" on a PR, respond to review comments, address reviewer suggestions, or work through unresolved review threads.
Pull request conventions and requirements. Use when creating a pull request, writing a PR description, preparing changes for review, or referencing the PR template.
MeshCore binary Companion Protocol conventions. Use when reading or writing anything in lib/meshcore/ — commands, responses, frame parsing, or transports.
TypeScript, React, and styling conventions for this project. Use when writing or reviewing any source file, adding components, or touching the state layer.