Loading...
Loading...
Found 111 Skills
This skill should be used when the user asks to commit changes, wants help writing commit messages, or has finished a task and needs to save their work. Triggers include: "commit this", "commit changes", "save my changes", "write a commit", "help me commit", "create a commit", "conventional commit", "/commit". Always confirms with user before committing. Never pushes to remote.
Generate commit messages following conventional commits and commit staged changes. Use when creating commits or when user invokes /commit.
Generate concise Git commit messages in imperative mood. Analyzes staged changes first; if none, examines unstaged and untracked files. Use when the user asks to create, write, draft, make, or generate a commit message.
Review full Git working tree changes and propose one or more safe, reviewable commit messages plus commit ordering. Use when the user asks for "git propose", asks how to split current changes into commits, or wants Conventional Commit messages from staged, unstaged, and untracked changes.
Git best practices for commit messages and branch workflow. Use when: - Writing, reviewing, or advising on a git commit message - Advising on branching strategy, merging, or rebasing - Setting up or explaining a team Git workflow - Preparing or reviewing a pull request - Resolving or advising how to avoid merge conflicts - Any task involving git history, linear history, or PR hygiene
Use When: Submitting code to a Git repository and generating standardized commit messages
Correct naming for a PR
Create well-formatted commits with conventional commit messages and emoji
Use when the user asks to commit changes, organize commits, write commit messages, or split working-tree changes into Conventional Commits. Trigger on phrases like "commit my changes", "커밋해줘", "커밋 분리", "make commits", "/conventional-commit", or whenever the user wants to turn current changes into Conventional Commit-style commits. For commit + push use `conventional-commit-push`; for rewriting non-Conventional commit history use `conventional-commit-rewrite`.
Create a git commit with conventional commit format. MUST use anytime you want to commit changes.
Commit staged changes with appropriate commit messages
Extract and parse local git commit history into structured JSON format with custom tags ([Why], [What], [Impact]). Use when generating changelogs, creating PR summaries, updating CHANGELOG.md files, or analyzing recent code changes. Parses conventional commits, extracts technical details and business impact, and returns flat JSON to save context tokens and reduce hallucinations during documentation generation.