git-commit-writer
Git Commit Writer
Write clear Conventional Commit messages from the actual git state. Prefer safe staging, precise scopes, and minimal commit bodies.
Workflow
-
Inspect the repository state before proposing a message.
- Check
git status --short. - Review staged diff first with
git diff --cached. - If nothing is staged, inspect
git diffand decide whether staging is required. - Do not assume all modified files belong in one commit.
- Check
-
Protect unrelated work.
- Keep user changes that are unrelated to the requested task out of the commit.
- If the worktree contains multiple concerns, recommend splitting commits.
- If the requested commit scope is ambiguous, state the assumption before committing.
-
Infer the commit intent from behavior, not filenames alone.
feat: visible or functional capability added
More from wibaek/skills
python-starter
Automatically configures formatter and linter settings when initializing Python projects. Installs ruff by default and uses pyproject.toml for configuration. Detects or asks the user about venv/poetry/uv environments and installs as dev dependencies. Optionally configures pre-commit and ty. Suggests VSCode workspace settings when using VSCode. Use this skill when starting Python projects ("Start a Python project", "Create a FastAPI project", "Create a data analysis Python project", etc.).
8ts-starter
Configure TypeScript project tooling for existing Node or frontend projects without app scaffolding. Use for TS starter setup, TS lint/format/test setup, Node TypeScript starter, or Vite TypeScript config requests.
6rest-api-guidelines
Design, review, and draft consistent HTTP+JSON REST APIs using resource-oriented design and long-term compatibility rules. Use when Codex needs to define or critique REST endpoints, OpenAPI contracts, URI and resource naming, HTTP method and PATCH semantics, status codes, pagination, versioning, error formats, or backward and forward compatibility policies.
3github-pr-writer
Draft GitHub pull request titles and structured PR bodies from branch history, diffs, and validation results. Use when Codex needs to write a PR description, summarize a branch for review, choose a base branch, prepare `gh pr create`, or open a pull request that follows the repository template.
2