// Formats GitHub commit messages following Conventional Commits style with a title and optional description. Use when proposing or implementing code changes, writing commit messages, or when the user asks for commit message suggestions.
Commit current work by reviewing diffs, splitting into logical commits, and writing standardized messages. Use when the user says "commit", "commit this", "commit current work", or asks to create a git commit.
Retrieve up-to-date documentation for software libraries, frameworks, and components via the Context7 API. Use when looking up documentation for a programming library, verifying APIs, or obtaining current library examples.
Systematic evidence-based debugging using runtime logs or focused reproductions. Use when the user reports a bug, unexpected behavior, or asks to debug an issue.
Scan recent changes for AI-generated code slop and remove it. Use when the user says "deslop", "remove slop", "clean up AI code", or asks to remove AI-generated artifacts from the codebase.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities.
Resolve all merge conflicts on the current branch non-interactively, validate the package, and commit. Use when the user says "fix merge conflicts", "resolve conflicts", or when git status shows conflicting files.
| name | commit-format |
| description | Formats GitHub commit messages following Conventional Commits style with a title and optional description. Use when proposing or implementing code changes, writing commit messages, or when the user asks for commit message suggestions. |
Title only:
> **Commit title:** `type(scope): short description here`
Title with description:
> **Commit title:** `type(scope): short description here`
>
> Description sentence one. Description sentence two with `codeRef()` references.
> prefix).**Commit title:** wrapped in exactly one backtick pair.fix, feat, perf, refactor, docs, chore, build, test.challenge, schema, tests, docs, release, or tooling.>.