oriolmatamoros/everOS / .claude/skills/commit
commit
UnverifiedStage and create a Conventional Commits message for the current change
/commit
Create a well-formed commit following the Conventional Commits
standard. The format is enforced by gitlint in the commit-msg hook.
Steps
-
Run
git statusandgit diff(andgit diff --staged) to see what changed. -
Review recent history for style:
git log --oneline -10. -
Group the change into a single focused commit. If the working tree mixes unrelated changes, stage selectively (
git add -p/ specific paths) rather than committing everything at once. -
Write the message in Conventional Commits form:
<type>[(scope)][!]: <imperative summary, ≤72 chars> <optional body: what & why, wrapped at 72> <optional footer: BREAKING CHANGE: …, Refs: #123> -
Never use
--no-verify. If pre-commit hooks fail, fix the cause and re-commit. -
Do not commit secrets, generated artifacts, or work-in-progress directly to the protected
mainbranch.
Types
| Type | Use for |
|---|---|
feat | new feature |
fix | bug fix |
refactor | behavior-preserving restructure |
test | add / update tests |
docs | documentation |
style | formatting only |
perf | performance |
chore | config / build / tooling |
build | build system or dependencies |
ci | CI configuration |
revert | revert a previous commit |
Notes
- No emoji — the title must start with the
type. - One logical change per commit; keep the history bisectable.
- The summary is imperative mood: "add", not "added" / "adds".
scopeis optional:fix(search): …. A!before the colon (or aBREAKING CHANGE:footer) marks a breaking change.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |