Skip to content

oprogramadorreal/optimus-claude / skills/commit

commit

Verified

Stages, commits, and optionally pushes local changes with a Conventional Commits message — always previews and confirms first, and offers a feature branch on protected branches. Modes: "suggest" proposes a message without committing (read-only); "branch [description]" creates and switches to a conventionally named branch, never committing or altering local changes. Multi-repo aware.

FileKindSize
README.mdmarkdown2.9 KB
SKILL.mdskill md7.0 KB
agents/openai.yamlconfig198 B
references/branch-naming.mdmarkdown1.5 KB
references/conventional-commit-format.mdmarkdown1.4 KB

references/branch-naming.md

View on GitHub
# Branch Naming Convention

Shared reference for generating feature branch names. Consumed by the commit, tdd, and worktree skills.

## Format

```
<type>/<slugified-description>
```

`<type>` is the conventional commit type that best describes the change: `feat`, `fix`, `refactor`, `docs`, `style`, `test`, `chore`, or `perf`.

## Type Detection Keywords

When inferring `<type>` from a description or context:

- "add", "implement", "create", "new" → `feat`
- "fix", "bug", "broken", "error", "crash" → `fix`
- "refactor", "restructure", "clean up", "simplify" → `refactor`
- "test", "coverage", "spec" → `test`
- "docs", "readme", "documentation" → `docs`
- "style", "format", "lint", "whitespace" → `style`
- "performance", "optimize", "speed", "cache" → `perf`
- "build", "ci", "dependency", "upgrade", "config" → `chore`
- When ambiguous, default to `feat` for new files or `fix` for modifications

## Slug Rules

Lowercase the description, replace spaces with hyphens, strip characters outside `[a-z0-9-]`, collapse consecutive hyphens, and trim leading/trailing hyphens. Truncate so the total branch name (`<type>/` + slug) stays at max 50 characters.

## Collision Handling

Default policy when the derived name already exists (`git show-ref --verify --quiet refs/heads/<branch-name>` succeeds): append `-2` to the slug; if taken, try `-3` through `-9`. If all collide, inform the user and stop.

## Examples

- `feat/add-user-authentication`
- `fix/login-validation-error`
- `chore/upgrade-eslint-to-v9`
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: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated 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: 322kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall