Menú
Commit all outstanding changes as standalone, logically coherent atomic commits using Conventional Commits.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Review a GitHub pull request against the shared review principles. Accepts "123" (current repo), "repo#123" (current repo's owner), "owner/repo#123", or a URL. Reports Issues and Notes locally, then optionally posts them to the PR as a review.
Review all outstanding changes — or, when the working tree is clean on a non-main branch, the branch's diff from the main branch. Reports Issues (anything that could cause user problems, security risk, or data inconsistency) and optional Notes for further improvement.
Review outstanding changes and surface the single most worthwhile improvement to make before committing. Returns one finding — not a list — and only if it's in scope for the change at hand.
Create a GitHub release. Commits and pushes outstanding changes first, then drafts release notes for confirmation. Deployment is only triggered if the project has a release-triggered workflow.
Bootstrap or sync the tobilize approach in the current project — a thin CLAUDE.md that imports @docs/approach.md plus a docs/ tree (architecture/, design/, domain/, plan/) with INDEX.md in each. Discovers project tooling and layout to seed real build commands and an initial architecture overview, not generic placeholders. Also offers method-specific guidance files (DDD, TDD, Hexagonal, SOLID).
Flesh out a draft file into publication-ready prose, respecting any local editorial guidance.
| name | commit |
| description | Commit all outstanding changes as standalone, logically coherent atomic commits using Conventional Commits. |
| disable-model-invocation | true |
| context | fork |
| allowed-tools | Bash(git add:*), Bash(git commit:*), Bash(git diff:*), Bash(git log:*), Bash(git push:*), Bash(git status:*) |
Commit all outstanding changes. Group related changes into standalone, logically coherent atomic commits. Each commit must be independently meaningful — do not lump unrelated changes together.
Run git status and git diff (both staged and unstaged) to understand all outstanding changes.
Run git log --oneline -25 to see recent commit style for reference.
Analyze the changes and group them into logical units. Each group should represent one coherent change (e.g., a single feature, a single bug fix, a refactor of one concern). Consider file relationships and semantic coupling when grouping.
For each logical group, in a sensible order (e.g., foundational changes first):
a. Stage only the files belonging to that group using git add <specific files>.
b. Commit with a simple one-liner: git commit -m "<type>: <description>"
feat, fix, refactor, test, docs, chore, style, perf, ci, buildgit commit -m "feat: add company search endpoint"$(), heredocs, or multi-line messagesAfter all commits, run git push to push everything to GitHub.
Run git log --oneline -<N> (where N = number of new commits) to show the user what was committed.
git add -A or git add . — always add specific files.