Loading...
Loading...
Found 262 Skills
Create standardized git commit messages. Prioritize following the project's existing commit conventions, and support the Conventional Commits format. Usage scenarios: Users request to create commits or write commit messages
Git version control with branching, merging, and rebasing. Use for source control.
lazygit terminal UI for git. Use for git operations.
Manage git repositories using the worktree pattern. This allows multiple branches to be checked out simultaneously in sibling directories.
Formats git commit messages according to Conventional Commits specification. Use this when the user asks to commit changes or write a commit message.
Summarizes git commits for specified users over a given time period and generates markdown reports
Intelligently detects when too many files are staged and automatically groups them by feature or functionality using Conventional Commits with user language preference
Safely clean merged and stale git branches with explicit confirmations.
Split git changes into context-based micro-commits
Working with GitHub Pull Requests using the gh CLI. Use for fetching PR details, review comments, CI status, and understanding the difference between PR-level comments vs inline code review comments.
Write detailed Conventional Commit messages using only the active chat conversation as context. Use when the user asks for commit messages based on discussion history, requests module-scoped commit subjects, or explicitly forbids checking git logs, diffs, or code files.
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.