Loading...
Loading...
Found 199 Skills
Generate commit messages following conventional commits and commit staged changes. Use when creating commits or when user invokes /commit.
Use When: Submitting code to a Git repository and generating standardized commit messages
Chinese Code Review Communication Reference - Script Templates, Priority Labeling (Must Fix/Suggested Change/For Reference Only), Countermeasures for Common Anti-patterns in Domestic Teams. Only invoke when the user explicitly uses /chinese-code-review, do not trigger automatically based on context.
Write a commit message body by deriving it from the code, not by summarizing the diff. Weighs the change, then either answers seven questions against the implementation — what forces it, which call paths reach it, how it failed, what breaks on update, what the tests pin — or produces a two-to-three-line body for mechanical and generated changes. Not for full commit creation.
Perform git commit following Conventional Commits standards
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
Chinese Code Review Guidelines - Provide effective feedback in a way that aligns with domestic team culture while maintaining professionalism and rigor
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`.
Create conventional commit messages. Use when the user says "commit this", "save changes", "git commit", asks to commit code, write a commit message, or format git history. Follows conventional commits specification.
Define and manage Git workflow rules in docs/rules/git/. Use when establishing commit message formats, branch naming conventions, PR requirements, code review standards, or any Git-related enforceable rules.
Commit and push vault changes to Git with smart commit messages. Auto-stages files, creates meaningful commits, and syncs with remote. Use after making vault changes or at end of day.
Use this skill to write, validate, or generate commit messages that follow the Conventional Commits specification.