Loading...
Loading...
Found 155 Skills
Generate commit messages following conventional commits and commit staged changes. Use when creating commits or when user invokes /commit.
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 creating git commits in this project
Use When: Submitting code to a Git repository and generating standardized commit messages
Smart git commit workflow using Conventional Commits format with AI-generated commit message suggestions based on staged changes.
Correct naming for a PR
Create well-formatted commits with conventional commit messages and emoji
Download files into a GitHub repository by writing special commit messages that trigger a GitHub Actions workflow.
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