Discover business git workflows skills, compare source repositories and read the instructions for each workflow.
Use when the user asks to clean up, delete, or remove a merged feature branch. Delegates to the specialized branch-cleanup sub-agent to safely delete both local and remote branches after comprehensive validatio...
Use when the user asks to address, fix, or handle CodeRabbit review feedback on GitHub Pull Requests. Delegates to the specialized coderabbit-fixer sub-agent to fetch new comments, apply fixes, run tests, and p...
This skill should be used when the user asks about "release process", "versioning", "semantic versioning", "semver", "release automation", "publishing", "package publishing", "release checklist", "version bump"...
This skill should be used when the user asks about "version control", "git workflow", "branching strategy", "commit messages", "conventional commits", "git hooks", "branch naming", "merge strategy", "PR require...
This skill should be used when the user asks about "project setup", "project initialization", "repository setup", "new project", "bootstrap project", "project structure", "development environment", "toolchain s...
This skill should be used when the user asks about "CI pipeline", "continuous integration", "GitHub Actions", "CI configuration", "CI jobs", "workflow", "CI caching", "CI environment", "pipeline structure", or...
Discovers relevant repositories and files for a given Jira ticket. Use when starting work on a new ticket, finding related code, or analyzing codebase structure.
Enriches Jira tickets created by Sentry with code analysis, relevant files, and creates a GitHub PR with the fix plan
Identify which repository contains the bug and which files are affected
Handle PR comment feedback and update the plan accordingly
Clean up git branches by analyzing merged/unmerged status, archiving completed work, and organizing active branches. This skill should be used when the user wants to clean up branches, organize their git reposi...
Show commit history for a file or the entire repository. Returns commit information including hash, author, date, and message.
Show changes between two commits or between a commit and the working tree. Returns file-by-file diff information including additions, deletions, and change hunks.
This skill should be used when the user asks to "create a worktree", "add a worktree", "set up a worktree", mentions "git worktree", or wants to work on multiple branches simultaneously.
This skill should be used when the user asks to "commit and push", "push my changes", or wants to commit, push, and respond to PR comments.
This skill should be used when the user asks to "fix PR comments", "address PR feedback", "resolve PR threads", mentions "PR review", or discusses GitHub pull request comments.
Create AI-executable TASK/FIX GitHub issue bodies (and optionally create/link them as sub-issues) for SUM Platform work orders. Use when converting a WO/idea/report into a deterministic task ticket that an agen...
Orchestrate the planning workflow (Idea → Plan → VD → WO → TASK/FIX) for SUM Platform releases and infrastructure initiatives. Use when starting a new version or initiative, creating planning artifacts, or gene...
Fully autonomous commit and push workflow. Verifies linting, types, tests, and build - fixes any issues automatically - then commits and pushes. NO user confirmation required at any step.
Implements GitHub issues that have approved implementation plans. Use when you need to implement an issue, create a branch, write code, and submit a PR. Requires a clear implementation plan in the issue comment...
Prevents Git Bash path conversion issues when running Anubis commands on Windows. Use when building targets with `cargo run` or `anubis.exe` that use `//` target paths.
Defines branch naming conventions for issue work. Use when creating branches for issues, understanding work status from branches, or linking commits to issues.
Local-first workflow for iterative document building with GitHub gists
Conventional commit format, type selection, and commit best practices
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.