Skip to content

oprogramadorreal/optimus-claude / skills/commit

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/conventional-commit-format.md

View on GitHub
# Conventional Commit Format

Shared reference for analyzing changes and generating conventional commit messages. Consumed by the commit and tdd skills.

## Analyze

Infer type, scope, and purpose from the gathered diffs. Untracked files appear only as names (`git status --short` produces no diff) — read their contents when needed. In a multi-repo workspace, analyze each repo independently.

## Capture implementation context

When run in the conversation where the changes were implemented, put the *why* the diff cannot show into the commit body: design decisions, trade-offs, alternatives rejected, deliberate non-goals. Omit process narration, restatement of what the diff already shows, and anything speculative. If no such context exists (e.g., a fresh conversation against pre-existing changes), rely on the diff alone — never fabricate context.

## Format

Always produce a Conventional Commits message, regardless of the repository's existing commit style:

```
<type>(<optional scope>): <description>

<optional body>
```

- Types: `feat`, `fix`, `refactor`, `docs`, `style`, `test`, `chore` (includes build, CI, dependencies), `perf`
- Subject under 72 characters, imperative mood; add a body only when the subject alone is insufficient

## Splitting

When changes span distinct concerns, propose separate commits — never force artificial splits when everything serves one purpose. Each proposal specifies the commit message and the exact files to stage.
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 CodeCodexUnverifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 318kUpdated Claude CodeCodexUnverifiedInstall
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 CodeCodexUnverifiedInstall
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 CodeCodexUnverifiedInstall