Loading...
Loading...
Found 192 Skills
Designs git workflows covering branching strategies, trunk-based development, stacked changes, conventional commits, CI/CD pipelines, and repository hygiene. Use when setting up branching models, writing commit messages, configuring GitHub Actions, managing stacked PRs, cleaning stale branches, creating issue templates, or recovering lost commits.
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 and push all local changes to remote repo
Use this skill when committing code, writing commit messages, or reviewing git history in this Next.js project. Triggers on: "commit this", "write a commit message", "what should my commit say", "git commit", or any request to stage and commit changes. Provides project-specific conventional commit format, Thai-language comment conventions, and scope rules matched to this codebase's structure.
Generate a git commit message and ready-to-run git commit command from the actual staged/working diff. Use whenever the user asks for a commit message, commit command, "/git-commit", or "commit this"; supports one-line commits, detailed commits, single-repo projects, and monorepo scoped commit bodies.
Analyzes git diffs or staged changes and generates narrative commit messages that explain WHY a change was made, not just what changed — following Conventional Commits format. Use when asked to "write a commit message", "generate a commit", "describe my changes", "what should I commit this as", "commit this", "summarize my diff", or "help me commit". Works with git diff output, staged files, or plain descriptions of changes.
Automatically creates semantic Git checkpoint commits during AI coding sessions. Replaces opaque platform checkpoints with transparent, queryable Git commits using Conventional Commits format with Git Trailers. You MUST follow this skill whenever you make code changes — commit after each meaningful edit.
Git Version Control & Collaboration Expert, covering GitHub/Gitee platform operations, Conventional Commits specifications, and PR/MR best practices.
Phase-gated git commit workflow with validation, staging, and CLAUDE.md compliance enforcement. Use when creating commits, staging changes, or when PR workflows need standardized commits. Triggers: "commit changes", "save work", "create commit", or internal skill invocation from PR workflows. Do NOT use for merge commits, rebases, amends, cherry-picks, or emergency rollbacks requiring raw git speed.
Generates properly formatted Git commit messages (title + description) following Conventional Commits. Use this skill whenever the user wants to write a commit message, document code changes in git format, or asks things like "how should I commit this?", "write a commit for these changes", "help me with my commit message", or describes what they changed and needs a git-ready output. Always use this skill when the user describes code changes and needs a commit, even if they don't explicitly say "commit".
[AUTO-INVOKE] MUST be invoked BEFORE creating git commits, PRs, or code reviews. Covers Conventional Commits, PR templates, review requirements, and AI-assisted development rules. Trigger: any task involving git commit, git push, PR creation, or code review.
Use when branching, committing, writing a CHANGELOG entry or opening a pull request against a Bagisto repository. Trigger phrases include "branch", "commit", "commit message", "PR", "pull request", "changelog", "merge", "conventional commits", "release notes".