Loading...
Loading...
Found 116 Skills
Workflow Specifications Adapted to Domestic Git Platforms and Team Habits - Full Coverage of Gitee, Coding, Jihu GitLab
Create Git commits with Conventional Commits analysis, safe staging, and concise message generation. Use when the user asks to commit changes or create a git commit.
Preparar y ejecutar git commit con mensajes Conventional Commits inferidos del diff (tipo, scope, descripción, staging). Activar cuando el usuario pida hacer commit, generar el mensaje, separar cambios en varios commits, o use invocaciones tipo `/commit`.
Write detailed Conventional Commit messages using only the active chat conversation as context. Use when the user asks for commit messages based on discussion history, requests module-scoped commit subjects, or explicitly forbids checking git logs, diffs, or code files.
Smart git commit with short, concise messages. Use when the user wants to commit changes, stage files, or create git commits.
Auto-generates conventional commit messages from git diffs with tiered format enforcement. Analyzes staged changes to produce meaningful commit messages following Conventional Commits specification.
Use this skill to write, validate, or generate commit messages that follow the Conventional Commits specification.
Use when creating git commits in this project
Use When: Submitting code to a Git repository and generating standardized commit messages
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.
A comprehensive Git assistant skill that provides intelligent branch management, commit message conventions, workflow assistance, and code review guidance. Automatically activates when users perform Git operations or use /git commands.
Create git commits using conventional commits with scopes. Use when the user asks to commit, make a commit, save changes, or any git commit operation. Never include Co-Authored-By lines, AI agent mentions, or any reference to Claude, AI, or automated tooling in commit messages.