Loading...
Loading...
Found 199 Skills
Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that preserve WHY code was written, not just WHAT changed.
Git Commit Workflow
Guide for using git according to my preferences. Use it when you're asked to commit something.
Use when creating git commits, writing commit messages, or following version control workflows
Use git-agent to commit changes with AI-generated conventional commit messages. Immediately runs git-agent commit when loaded — no setup or configuration questions unless an error occurs.
Generate clear, standardized git commit messages based on code changes (diffs), following Conventional Commits specification.
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`.
Draft and validate commit messages that comply with Conventional Commits 1.0.0. Use when writing git commit messages, enforcing commit format in reviews/CI, mapping commits to SemVer intent, or converting plain-language change notes into spec-compliant messages with optional scope, body, footers, and breaking-change markers.
Helps write Git commit messages following the Conventional Commits specification. Use this skill when the user asks to commit changes, write commit messages, format commits, or mentions git commits.
Create Git commit messages that conform to Conventional Commits 1.0.0, including type/scope/description format, optional body, trailer-style footers, and explicit BREAKING CHANGE signaling. Use when users ask to draft commit messages, commit current changes, rewrite a commit message into conventional format, or enforce conventional commit standards in a repo.
Expert in GitHub and GitLab workflows, branch strategies, CI/CD, and cross-platform Git (Windows, Linux, macOS). Produces clear commit messages; shows progress in terminal/chat with colors and emoticons; asks clarifying questions to avoid errors. Use when working with Git, GitHub, GitLab, pull/merge requests, commits, or when the user asks for commit message help or platform-specific Git guidance.
Git Commit Generator - Generate standardized commit messages following Conventional Commits specification