alamenai/terrae / .claude/skills/commit
commit
VerifiedCreate standardized git commits following Terrae's conventions
Commit Skill
Create standardized git commits following Terrae's conventions.
Instructions
-
Check Current State
- Run
git statusto see changed files - Run
git diffto see the actual changes
- Run
-
Review Changes with User
- Summarize what files were changed
- Explain the nature of changes (new feature, bug fix, refactor, etc.)
- Ask the user if they want to proceed with the commit
-
Stage Files
- Stage specific files by name (avoid
git add -Aorgit add .) - Never stage sensitive files (.env, credentials, etc.)
- Stage specific files by name (avoid
-
Commit Message Format Follow conventional commits:
type(scope): descriptionTypes:
feat: New featurefix: Bug fixdocs: Documentation changesstyle: Formatting, no code changerefactor: Code restructuringtest: Adding or updating testschore: Maintenance tasks
Examples:
feat(marker): add rotation supportfix(popup): prevent memory leak on unmountdocs(readme): update installation instructions
-
New Component Convention
When committing a new component, split into 3 separate commits in this order:
feat(map): add {component} component— the source file (src/registry/map/{slug}.tsx)feat(docs): add {component} example components— all example files (src/app/docs/_components/examples/{slug}-*.tsx)feat(docs): add {component} documentation page— the docs page (src/app/docs/{slug}/page.tsx)
Shared file modifications (sidebar, components page, changelog, registry.json, barrel export) should be committed separately since they often contain changes for multiple components.
-
Important Rules
- Do NOT add
Co-Authored-Bylines - Do NOT commit until user approves
- Do NOT use
--amendunless explicitly requested - Do NOT push unless explicitly requested
- Keep commit messages concise (under 72 characters)
- Do NOT add
-
Create the Commit
git commit -m "type(scope): description" -
Verify
- Run
git statusto confirm commit succeeded - Show the commit hash to the user
- Run
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 |