Skip to content

erode-app/erode / .agents/skills/git-commit

git-commit

Verified

Conventional 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

TypeUse for
featNew functionality visible to users
fixBug fixes
docsDocumentation-only changes
styleFormatting, whitespace, no logic change
refactorCode restructuring, no behavior change
testAdding or updating tests only
buildBuild system, dependencies, Docker
ciCI/CD pipeline changes
choreMaintenance that doesn't fit elsewhere

Scopes

  • core — changes scoped to packages/core/
  • cli — changes scoped to packages/cli/
  • web — changes scoped to packages/web/
  • architecture — changes scoped to packages/architecture/
  • eslint-config — changes scoped to packages/eslint-config/
  • deps / deps-dev — dependency bumps
  • release — 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-123 when closing a Linear issue

Instructions

When asked to commit:

  1. Run git status (never use -uall) and git diff --cached to understand staged changes
  2. If nothing is staged, identify which files should be staged based on the user's intent
  3. Pick the correct type and scope from the tables above
  4. Write a concise subject line in imperative mood
  5. Add a body only when the "why" isn't obvious from the subject
  6. Use a HEREDOC for the commit message to preserve formatting
  7. Never amend unless the user explicitly asks
  8. Never skip hooks (no --no-verify)
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 implementationStars: 318kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 318kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 318kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 318kUpdated Claude CodeCodexVerifiedInstall