Loading...
Loading...
Found 305 Skills
A comprehensive Git agent skill combining strategic workflows, strict conventional commit standards, and safe execution protocols. Acts as a senior engineer to guide users through atomic, verifiable, and standardized git operations.
Git Commit Rules
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.
Summarizes git commits for specified users over a given time period and generates markdown reports
Generate professional git commit messages following Conventional Commits specification. Use when user asks to commit changes or write a commit message.
Generate conventional commit messages automatically. Use when user runs git commit, stages changes, or asks for commit message help. Analyzes git diff to create clear, descriptive conventional commit messages. Triggers on git commit, staged changes, commit message requests.
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".
Use when the user needs help with conventional commits, semantic versioning, changelog generation, or commit message quality improvement. Triggers: user says "commit", "version bump", "changelog", "commit message", staging changes for commit, preparing a release.
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.
Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.
Commit changes and push to origin without creating a PR