Loading...
Loading...
Found 199 Skills
Stage and commit changes with conventional commit message
Analyze staged Git changes and generate a concise Chinese commit message that follows repository commit style. Use when the user asks to commit code, generate a commit message, or summarize staged changes into a Chinese Git commit title and bullets.
Creates a new git commit for all uncommitted changes with an atomic, conventionally-tagged message. Use when work is complete and ready to be committed.
Generate concise, descriptive git commit messages following best practices. Use when creating git commits from staged changes, crafting commit messages, or reviewing commit message quality. Use when the user says /commit or asks to create a git commit.
Helps users create standardized Git commits. Use this when users want to submit code, save changes, or create a commit.
Create conventional commit messages following best conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits specification.
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point
Use when creating git commits in this project
Git Workflow Standard Operating Procedures, including commit message generation and remote repository synchronization
Fetch upstream, rebase, stage all changes, run ADR compliance check on modified artifacts, generate a descriptive commit message from the diff, commit, and push to the current branch's upstream. Handles merge conflicts by preferring local changes for config/project files and upstream for scaffolding.
Generate clear, conventional commit messages from staged changes. Use when the user asks to commit or needs a commit message.
Generate a git commit message compliant with Conventional Commits 1.0.0 (and the de facto @commitlint/config-conventional rules) from currently staged changes. Outputs Korean by default, or another language if the user explicitly requests it. Trigger when the user asks for a commit message — e.g. "/conventional-commits", "write a commit message", or any equivalent. Scope is limited to producing the message text; executing `git commit` is outside this skill's responsibility.