erode-app/erode / .agents/skills/git-commit
git-commit
VerifiedConventional commits with project conventions. Use when the user asks to commit, make a commit, or wants to follow the project's git commit standard.
Git Commit Standard
All commits in this project follow the Conventional Commits spec, tailored
for a monorepo with packages/core/, packages/cli/, and packages/web/.
Subject Line
type(scope): description
- Lowercase everything
- Imperative mood ("add", not "added" or "adds")
- No trailing period
- Max 72 characters
Types
| Type | Use for |
|---|---|
feat | New functionality visible to users |
fix | Bug fixes |
docs | Documentation-only changes |
style | Formatting, whitespace, no logic change |
refactor | Code restructuring, no behavior change |
test | Adding or updating tests only |
build | Build system, dependencies, Docker |
ci | CI/CD pipeline changes |
chore | Maintenance that doesn't fit elsewhere |
Scopes
core— changes scoped topackages/core/cli— changes scoped topackages/cli/web— changes scoped topackages/web/architecture— changes scoped topackages/architecture/eslint-config— changes scoped topackages/eslint-config/deps/deps-dev— dependency bumpsrelease— release automation changes- Omit scope for repo-wide or cross-package changes
Body
- Explain why, not what (the diff shows what)
- Wrap at 72 characters
- Include
Resolves ABC-123when closing a Linear issue
Instructions
When asked to commit:
- Run
git status(never use-uall) andgit diff --cachedto understand staged changes - If nothing is staged, identify which files should be staged based on the user's intent
- Pick the correct type and scope from the tables above
- Write a concise subject line in imperative mood
- Add a body only when the "why" isn't obvious from the subject
- Use a HEREDOC for the commit message to preserve formatting
- Never amend unless the user explicitly asks
- Never skip hooks (no
--no-verify)
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: 318k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 318k | 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: 318k | 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: 318k | Updated | Claude CodeCodex | Verified | Install |