Loading...
Loading...
Found 174 Skills
Review code changes against a plan using the plan location and implementing git commit(s).
Dispatch code-reviewer agent for two-stage review. Use after completing implementation tasks.
Always apply this skill when committing to git
Tidy workspace, create semantically meaningful commits, and push. Analyzes changes, categorizes files (commit/gitignore/delete/consolidate), groups into logical commits with conventional prefixes. Use when: ready to commit, cleaning workspace, pushing changes.
Commit recent changes that haven't yet been commited.
Commit changes to git with a descriptive conventional commit message. Use when ready to commit staged or unstaged changes.
Undo the last commit while keeping changes staged. Use when you need to fix a commit message or add missing files.
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.
High-level workflows for managing work using Fizzy cards — start, work on, complete, and delegate cards using the Fizzy CLI.
Execute an implementation plan step-by-step with completion tracking. Use when the user wants to work through a plan, implement tasks sequentially, track progress on a task list, or asks to "execute the plan" or "start implementing".
Create git commits following the Conventional Commits v1.0.0 specification (conventionalcommits.org). Use when the user asks to commit changes, says "/conventional-commit", or wants a well-structured commit message. Triggers on requests like "commit this", "commit my changes", "create a commit", or any git commit workflow. Analyzes staged/unstaged changes and produces compliant commit messages with proper type, scope, description, body, and footers.
Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.