Loading...
Loading...
Found 199 Skills
Create git commits in Conventional Commits format. Use whenever committing changes or writing a commit message.
Generate Conventional Commit messages by inspecting current staged Git changes or using provided staged Git context. Use when asked to write a commit message, summarize staged changes, or classify a change as feat/fix/refactor/docs/test/build/ci/style/perf.
MUST be used whenever writing, amending, squashing, or auditing any Git commit message. Enforces subject-only defaults, bans AI attribution trailers and development diaries.
Smart Commit - stages all changes and creates a conventional commit
Invoke the skill `git:message` to generate a commit message, then create the Git commit non-interactively. Use when you need to commit either the already-staged changes or the full current working tree relative to `HEAD`, while preserving a review-friendly message and footer handling. Trigger for requests such as the skill `git:commit` or the skill `git:commit` with `HEAD`, especially when the user wants safe staging behavior and a clean commit created from the drafted message.
Generate a git-log-review-friendly commit message from repository changes. Use when you need to inspect staged changes, the current working tree relative to `HEAD`, or a commit-to-working-tree range and draft only the commit message text in a conventional-commit-style format, without creating the commit. Trigger for requests such as the skill `git:message`, the skill `git:message` with `staged`, the skill `git:message` with `HEAD`, or the skill `git:message` with `<commit>`, especially when the user wants a squash-ready summary of the most important changes.
Use when the user asks to create, revise, or execute a Git commit. Generates an accurate Conventional Commit message and only stages or commits files when explicitly requested.