Loading...
Loading...
Found 4,067 Skills
Apply the canonical GitHub issue and pull-request label set to a repository.
Manage git repositories using the worktree pattern. This allows multiple branches to be checked out simultaneously in sibling directories.
Smart Commit - stages all changes and creates a conventional commit
Isolated workspace creation - creates git worktrees with smart directory selection and safety verification for parallel feature development.
Merge changes from worktrees into current branch with selective file checkout, cherry-picking, interactive patch selection, or manual merge
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions via Rube MCP (Composio). Manage code workflows, review PRs, search code, and handle deployments programmatically.
Invoke the skill `git:message` to generate a commit message, then create the Git commit non-interactively. Use when you need to commit either the already-staged changes or the full current working tree relative to `HEAD`, while preserving a review-friendly message and footer handling. Trigger for requests such as the skill `git:commit` or the skill `git:commit` with `HEAD`, especially when the user wants safe staging behavior and a clean commit created from the drafted message.
Generate a git-log-review-friendly commit message from repository changes. Use when you need to inspect staged changes, the current working tree relative to `HEAD`, or a commit-to-working-tree range and draft only the commit message text in a conventional-commit-style format, without creating the commit. Trigger for requests such as the skill `git:message`, the skill `git:message` with `staged`, the skill `git:message` with `HEAD`, or the skill `git:message` with `<commit>`, especially when the user wants a squash-ready summary of the most important changes.
Configure GitLab authentication for Cyrus — glab CLI login and git config for creating merge requests.
Set up Claude Code hooks to intercept dangerous Git commands (push, reset --hard, clean, branch -D, etc.) before execution. Use this when users want to prevent destructive Git operations, add Git security hooks, or block git push/reset in Claude Code.
(NS) Sync existing GitLab issues with local planning and execution — milestone, RF labels, status transitions, assignee, estimates, spent time. Use during implementation when tasks link to GitLab issues or after plan-version-from-gitlab sync — not for creating new issues (use mcp-gitlab-usage). Always use atomic set_issue_labels and three-step status cycle. Read mcp-gitlab-usage for tool contracts.