Loading...
Loading...
Found 140 Skills
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.
Create git commits in Conventional Commits format. Estimate type/scope from staged changes, detect breaking changes and secret leaks (such as .env files). Must pass pre-commit hooks (`--no-verify` is not allowed). Use with instructions like "commit", "git commit", "record changes".
Git Commit Generator - Generate standardized commit messages following Conventional Commits specification
Refines code changes for better reviewability. Validates change cohesion (no mixed concerns), generates clear commit messages, creates PR/MR with reviewer-focused descriptions. Use when committing, reviewing, creating PR/MR, or mentions "commit", "review", "PR", "MR", "pull request", "merge request", "refine", "提交", "审查".
Guía para generar mensajes de commit en español siguiendo Conventional Commits estrictos con Emojis. Usa esta skill siempre que el usuario pida hacer un commit, generar un mensaje de commit, commitear cambios, o cuando se complete un cambio de código y sea momento de registrarlo en git. También se activa con 'commit', 'commitear', 'guardar cambios', 'registrar cambios' o cualquier intención de crear un punto en el historial de git.
Review, organize, and commit pending changes. Split into logical commits, stage carefully, and write clear Conventional Commit messages. Use when the user asks to commit, stage changes, or organize work into commits.
Git operations guide. Provides how-to for common git tasks. Use when: - Writing commit messages (Conventional Commits format) - Understanding git workflows
AUTOMATICALLY invoke this skill whenever git commit is needed - no user request required. Direct git commit will FAIL validation. This skill contains required pre-commit setup. Triggers: "커밋해", "커밋 ㄱㄱ", "커밋 만들어줘", "커밋 찍어줘", or ANY situation requiring git commit.
Set up and configure Git pre-commit hooks for code quality, secrets scanning, and commit message validation. Use when installing git hooks, configuring pre-commit checks, or enforcing code standards.
Review local git changes and perform a light code review. If no issues are found, commit the changes. Does NOT write or modify code — only reviews and commits. Optionally accepts a commit message header as an argument.
Generate conventional commit messages automatically. Use when user runs git commit, stages changes, or asks for commit message help. Analyzes git diff to create clear, descriptive conventional commit messages. Triggers on git commit, staged changes, commit message requests.
Writes and reviews Conventional Commits commit messages (v1.0.0) to support semantic versioning and automated changelogs. Use when drafting git commit messages, PR titles, release notes, or when enforcing a conventional commit format (type(scope): subject, BREAKING CHANGE, footers, revert).