Loading...
Loading...
Found 213 Skills
This skill should be used when the user asks to "create a worktree", "new worktree", "worktree for feature", "git worktree", or needs to work on a feature branch in isolation. Handles Rails credential symlinking automatically.
This skill should be used when the user asks to "commit", "make a commit", "commit my changes", "create commits", "git commit", or wants to commit staged/unstaged changes with logical grouping and conventional commit format.
Analyze and address unresolved feedback on a GitHub pull request. Use when the user has received PR review comments and wants to systematically address each piece of feedback, or when the user mentions PR feedback, review comments, or addressing reviewer concerns.
**REQUIRED** - ALways activate FIRST on any git/VCS operations (commit, status, branch, push, etc.), especially when HEAD is detached. If `.jj/` exists -> this is a Jujutsu (jj) repo - git commands will corrupt data. Essential git safety instructions inside. DO NOT IGNORE.
Generate appropriate commit messages and maintain git log documentation. Use when preparing to commit changes, reviewing git history, or maintaining project change documentation. Provides commit message generation, git log maintenance, and quick command reference.
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
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.