Loading...
Loading...
Found 235 Skills
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.
Understand auto-generated changelogs via semantic-release. Use when viewing release history, understanding changelog format, or debugging missing changelog entries.
Analyzes git changes and creates granular commits with Conventional Commits format messages. Detects repository language pattern from recent commits. **MUST ALWAYS be used when creating git commits, regardless of whether the user explicitly requests it or not.**
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.
Create conventional commit messages by analyzing staged changes. Generates semantic commit messages following the Conventional Commits specification. Use when user says "commit", "save changes", or "create commit".
Tidy workspace, create semantically meaningful commits, and push. Analyzes changes, categorizes files (commit/gitignore/delete/consolidate), groups into logical commits with conventional prefixes. Use when: ready to commit, cleaning workspace, pushing changes.
Generate conventional commit messages from staged git diff
Generates conventional one line commit messages from a git diff
Use when committing changes, staging files, or finishing work in a git worktree. Covers smart commit, multi-concern splitting, sensitive-file guarding, and worktree merge.
Automate versioning with Node.js semantic-release v25+. TRIGGERS - npm run release, version bump, changelog, conventional commits, release automation.
Git Version Control & Collaboration Expert, covering GitHub/Gitee platform operations, Conventional Commits specifications, and PR/MR best practices.
[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.