Loading...
Loading...
Found 164 Skills
View and manage inline GitHub PR review comments with full thread context from the terminal
Review a PR and submit suggestions as comments, along with an optional approval/request for changes.
Use when new insights change the scope, acceptance criteria, domain language, or technical constraints of an existing Epic, Feature, or Task — for example "refine epic
Add line-specific review comments to pull requests using GitHub CLI API
Patterns for invoking the GitHub CLI (gh) from agents. Covers structured output, pagination, repo targeting, search vs list, gh api fallback.
Push the current feature branch and open a pull request, ready for review. Use after a ticket's implementation is committed on its own branch — it detects the base branch, pushes, opens the PR with a clear body (summary · what changed · validation status), and returns the URL to hand to a reviewer.
Generate and manage changelogs from git history. Use for release notes, tracking breaking changes, and maintaining project history.
Workflow for repository reconnaissance and operations using GitHub CLI (gh). Optimizes token usage by using structured API queries instead of blind file fetching.
Publish a workflow learning to the groovebook shared commons as a GitHub PR. Use after groove-work-compound when a learning is worth sharing.
Push current branch changes to origin and create or update the corresponding pull request; use when asked to push, publish updates, or create pull request.
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
Use when checking live Capy task or PR state through Brave, Computer Use, or a Capy browser panel.