Loading...
Loading...
Found 116 Skills
Generate clear, conventional commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or preparing commits.
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.
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.
Guide for using git according to my preferences. Use it when you're asked to commit something.
Use when creating git commits to ensure commit messages follow project standards. Applies the 7 rules for great commit messages with focus on conciseness and imperative mood.
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.
Create one or more Conventional Commits following the spec and push the current branch. Use when the user asks to create commits, write a conventional commit message, commit and push changes, or prepare commits before opening a pull request.
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.
Draft, rewrite, and validate Odoo-style commit messages using [TAG] module: summary format, 50/72 length limits, imperative English, WHY-first body, and correct tag selection. Includes optional migration tagging ([MIG]) when the project workflow (like OCA) uses it.
Create a git commit with a clear, value-communicating message. Use when the user says "commit", "commit this", "save my changes", "create a commit", or wants to commit staged or unstaged work. Produces well-structured commit messages that follow repo conventions when they exist, and defaults to conventional commit format otherwise.
commit changes to git with a message derived from the diff only, ignoring session context like reviews or discussion. Skips hooks with -n by default; --verify runs them. Triggers: /commit, commit changes, save work to git, write a commit message. Flags: --staged/--unstaged for scope, --conventional/--simple for style, --verify to run hooks.
Quick-reference card for all hui modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /hui-help, "hui help", "what hui commands", "how do I use hui".