Loading...
Loading...
Found 23 Skills
Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.
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.
Generate exactly one high-quality Conventional Commit message from the current Git diff. Use when Codex needs to inspect staged changes, summarize the dominant intent, and return only the final commit message with no analysis or extra text.
Apply Spatie's version control conventions when creating commits, branches, pull requests, or managing Git repositories; use for naming repos, writing commit messages, choosing branch strategies, and merging code.
Use when writing, rewriting, or reviewing PR/CL descriptions, commit messages, or code-change summaries that explain what changed and why. TRIGGER on "write PR description", "improve this commit message", "summarize this diff", "CL description", "change description", or "make this PR/CL description easier to review". DO NOT TRIGGER for code review, PR splitting, code restructuring, user-facing changelogs, or reviewer replies unless the requested output is a change description.
Generate commit messages following conventional commits and commit staged changes. Use when creating commits or when user invokes /commit.
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.
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
Stage and commit the intended changes with a clear message.
Stage changes, draft conventional commit messages, and commit with user confirmation. Use when user types /commit, asks to commit changes, or mentions creating a git commit.
Cria mensagens de commit no estilo Conventional Commits — usar quando o usuário pede "commit", "git commit", ou após mudanças prontas para serem registradas no histórico.