Loading...
Loading...
Found 79 Skills
Generate comprehensive PR descriptions following repository templates
Use this skill when you need to perform Git operations such as committing changes, creating branches, merging, resolving conflicts, managing remotes, or any other Git-related tasks.
Identify and clean up stale git branches locally and on remotes with safe, reversible steps. Use when asked to prune, list, or delete merged/old branches or audit branch hygiene.
Addresses all PR review comments, resolves merge conflicts, and fixes failing CI checks to get the PR ready to merge. Use when the user wants to make their PR "all green" or ready for merge.
Manage stacked branches and pull requests with the gh-stack GitHub CLI extension. Use when the user wants to create, push, rebase, sync, navigate, or view stacks of dependent PRs. Triggers on tasks involving stacked diffs, dependent pull requests, branch chains, or incremental code review workflows.
View and manage inline GitHub PR review comments with full thread context from the terminal
Use after creating PR - monitor CI pipeline, resolve failures cyclically until green or issue is identified as unresolvable
This skill should be used when the user asks to "create a pull request", "create PR", "open PR", "update a pull request", "update PR", "create an issue", "file an issue", "create a GitHub issue", "create a Claude Code issue", "report a bug in Claude Code", "create a Codex issue", "report a bug in Codex CLI", "create a Sablier issue", "file an issue in sablier-labs", "create a discussion", "start a GitHub discussion", or mentions OSS contribution workflows.
Automatically creates comprehensive pull requests to the dev branch when user indicates their feature/fix is complete and ready for review. Use when user mentions creating PR, submitting for review, or indicates work is done. Examples - "create a PR", "ready for review", "open a pull request", "submit this to dev", "all tests passing, let's get this reviewed".
This skill should be used when a designer is picking up a Task issue to add design coverage. Triggers on phrases like "I want to design task
This skill should be used when a developer wants to open a pull request for a completed task branch — for example "create a PR", "open a pull request", "submit this for review", "make a PR for task
Commit changes and create a pull request to the official upstream repo