Loading...
Loading...
Found 162 Skills
Conventional Commits v1.0.0 standards for git messages. Use when (1) creating git commits, (2) writing or drafting commit messages, (3) reviewing commit message format, (4) explaining commit conventions, or (5) validating commit message compliance.
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
Create a git commit following project conventions
Automates git commits with WBS tracking and code review. Use when user wants to commit changes or needs commit message suggestions. Keywords: commit, 커밋, 커밋해줘, 커밋 메시지, git commit, WBS, 리뷰
Commit recent changes that haven't yet been commited.
Git conventions and workflow best practices including Conventional Commits, branch naming, and commit message guidelines. Use when user needs guidance on git standards, commit formats, or workflow patterns.
Create an appropriate git commit from the working tree and session history. Default commit messages are in Japanese unless the repo says otherwise (e.g. AGENTS.md).
Formats git commit messages according to Conventional Commits specification. Use this when the user asks to commit changes or write a commit message.
Generate git commits following Conventional Commits (commitlint). Use when user wants to commit changes.
Create git commits with user approval and no Claude attribution
Groups related git changes into coherent commits and drafts commit messages. Use when the user asks to commit, commit current changes, or create a commit.
Always apply this skill when committing to git