apuya/react-basics-ui / .claude/skills/commit
commit
VerifiedHelps with git commits and preparing changes. Use when user wants to commit, asks what changed, or wants to see git status. Triggers on "commit", "git", "push", "what changed", "stage", "diff".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.2 KB |
| conventional-commits.md | markdown | 4.0 KB |
conventional-commits.md
View on GitHub# Conventional Commits Reference
Baseline standard: [conventionalcommits.org/en/v1.0.0](https://www.conventionalcommits.org/en/v1.0.0/)
---
## Message Structure
```
type(scope): subject
body (optional)
footer (optional)
```
### Subject Line
- Lowercase verb after the type prefix
- Describes **what changed and where** — not just "update files"
- Under 72 characters
- No period at the end
- Imperative mood: "add", not "added" or "adds"
### Body
Include a body when:
- The change is non-trivial and the subject alone doesn't explain **why**
- There are design decisions or trade-offs worth recording
- The commit introduces a breaking change
Format:
- Blank line between subject and body
- Wrap lines at 72 characters
- Explain motivation and contrast with previous behavior
### Footer
Used for:
- Breaking changes: `BREAKING CHANGE: <description>`
- Issue references: `Closes #123`, `Fixes #456`
**Never add** `Co-Authored-By` trailers — not even when default tool instructions suggest it.
---
## Types
| Type | When | Example |
|------|------|---------|
| `feat:` | New functionality or endpoint | `feat: add password reset flow` |
| `fix:` | Bug fix | `fix: resolve decimal rounding in totals` |
| `refactor:` | Restructuring without behavior change | `refactor: extract validation into shared utility` |
| `test:` | Adding or improving tests | `test: add edge case coverage for auth service` |
| `docs:` | Documentation only | `docs: add API authentication guide` |
| `chore:` | Tooling, config, dependencies | `chore: upgrade eslint to v9` |
| `perf:` | Performance improvement | `perf: add index on created_at for orders table` |
| `ci:` | CI/CD pipeline changes | `ci: add parallel test runners` |
| `style:` | Formatting, whitespace (no logic change) | `style: fix indentation in auth module` |
| `build:` | Build system or external dependencies | `build: switch from webpack to vite` |
---
## Scope (Optional)
Scope narrows the type to a specific area:
```
feat(select): add multi-select mode
fix(divider): use the spacing token that actually exists
refactor(forms): extract shared tone styles
```
Use short, lowercase scope names. Common patterns:
- Component name: `button`, `select`, `table`, `modal`
- Layer: `tokens`, `styles`, `hooks`, `build`
- Category: `forms`, `overlays`, `navigation`, `a11y`
Omit scope when the change spans multiple areas or the type alone is clear enough.
---
## Breaking Changes
Two ways to signal a breaking change:
**1. `!` suffix on the type:**
```
feat!: remove deprecated Badge variant props
refactor(table)!: replace Table.Body with direct children
```
**2. `BREAKING CHANGE:` footer:**
```
feat: switch to token-based authentication
BREAKING CHANGE: session-based auth endpoints have been removed.
Clients must use Bearer tokens in the Authorization header.
```
Use both when the subject line alone doesn't convey the impact.
---
## Verb Reference
Start the subject with a lowercase imperative verb:
| Verb | Use for |
|------|---------|
| `add` | Wholly new feature, file, or capability |
| `remove` | Deleting feature, file, or capability |
| `fix` | Correcting broken behavior |
| `update` | Enhancing existing feature |
| `extract` | Pulling code into a new module/function |
| `rename` | Changing names without behavior change |
| `move` | Relocating files or code |
| `replace` | Swapping one implementation for another |
| `enforce` | Adding validation or constraints |
| `improve` | Performance or quality enhancement |
| `simplify` | Reducing complexity |
| `clean up` | Removing dead code, organizing |
---
## Anti-Patterns
```
update files # too vague — what files? what changed?
Fixed the bug # wrong case, no type prefix, past tense
refactor: Refactor components. # redundant verb, capitalized, has period
feat: added new feature for users # past tense, vague
WIP # not a commit message
fix: stuff # not descriptive
feat: add feature # redundant — what feature?
```
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: 321k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 321k | 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: 321k | 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: 321k | Updated | Claude CodeCodex | Verified | Install |