Loading...
Loading...
Found 31 Skills
Turn the working tree into logical, atomic Conventional Commits — classify uncommitted files as in-scope vs out-of-scope against the branch's merge base, show a staging plan, and create one commit per coherent unit (type + optional scope + British-English body; `!` / `BREAKING CHANGE:` for breaking changes). Never `git add -A`; files that look like they belong to another branch/worktree are never staged silently. Use when asked to commit uncommitted work, tidy WIP into atomic commits, or as the commit step inside a ship flow (e.g. `/send-it`). It commits only — no push, PR, changelog, or Linear writeback.
Create git commits following Conventional Commits specification with project-specific branch naming rules
Phase-gated git commit workflow with validation, staging, and CLAUDE.md compliance enforcement. Use when creating commits, staging changes, or when PR workflows need standardized commits. Triggers: "commit changes", "save work", "create commit", or internal skill invocation from PR workflows. Do NOT use for merge commits, rebases, amends, cherry-picks, or emergency rollbacks requiring raw git speed.
Create semantic git commits following Conventional Commits specification. Use when committing changes, making commits, or when asked to commit.
Code generation with Codex delegation. Understands task, finds patterns, delegates to Codex, validates output. Use when: implementing a feature, writing code, building functionality.
Handles commit flows by detecting changes, optionally running validator validation, and completing commits for requests such as "commit with validator", "run checks before commit", "run validator then commit", or "skip validator and commit".
Generate semantic commit messages following conventional commits format. Use when committing code, staging changes, writing commit messages, requesting git commit, or when user mentions commit, commit message, conventional commits, semantic commits, git commit, stage changes, create commit. Supports monorepo package version tracking.
Creates commits with conventional format and validation. Use when committing changes or generating commit messages.
Guide safe, repository-aware Git commits and pushes. Inspect repository policy, working-tree state, diffs, hooks, tests, branch/upstream configuration, and commit conventions before any mutation. Never commit, push, stage, restore, or discard changes without explicit authorization for that side effect. Use Conventional Commits only when repository policy or the user requires it.
Analyzes files modified with git commands and creates appropriately granular commits in logical units. Only activates when the skill name (committer) is explicitly specified, such as "/committer", "use the committer skill", or "commit with committer". Does not activate for general requests like "commit" or "git commit".
**REQUIRED** - ALways activate FIRST on any git/VCS operations (commit, status, branch, push, etc.), especially when HEAD is detached. If `.jj/` exists -> this is a Jujutsu (jj) repo - git commands will corrupt data. Essential git safety instructions inside. DO NOT IGNORE.
Use when committing changes, staging files, or finishing work in a git worktree. Covers smart commit, multi-concern splitting, sensitive-file guarding, and worktree merge.