Loading...
Loading...
Found 51 Skills
Resolve all PR comments using parallel processing. Use when addressing PR review feedback, resolving review threads, or batch-fixing PR comments.
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
Completes one or more tasks. Creates one tested and reviewed pull request for each task. Use to implement, build, fix, or deliver tasks, tickets, pull requests, or a milestone.
Request or contribute a new sales/marketing/GTM skill that doesn't exist yet. Use when no existing skill covers the user's need — helps them build the skill and submit a PR, or file an issue requesting it. Also use when the user says 'there should be a skill for this', 'can we make a skill', 'I want to contribute a skill', or 'none of the sales skills cover my use case'.
gh when inspecting a PR, reading review threads, diagnosing red CI, or composing non-trivial gh commands. fix-pr hunt invokes the scripts for surfaces 1–2 and CI snippets.
Creates Pull Requests for Prowler following the project template and conventions. Trigger: When working on pull request requirements or creation (PR template sections, PR title Conventional Commits check, changelog gate/no-changelog label), or when inspecting PR-related GitHub workflows like conventional-commit.yml, pr-check-changelog.yml, pr-conflict-checker.yml, labeler.yml, or CODEOWNERS.
Auto-fix CodeRabbit review comments - get CodeRabbit review comments from GitHub and fix them interactively or in batch
Write nurb.dev changelog entries from the releases since the last published one. Filters the release's merged PRs to what a user would actually notice, drafts each in the site's voice, and inserts the release into site/changelog.html. Use when the user says "changelog", "update the changelog", "announce this", or after cutting a release.
Sync local changes to GitHub in one command: detect state, branch, commit, push, create PR. Use when user wants to push work to GitHub, create a PR, or sync a feature branch. Use for "push my changes", "create a PR", "sync to GitHub", "open pull request", or "ship this". Do NOT use for reviewing PRs (use /pr-review), cleaning up after merge (use pr-cleanup), or CI checks (use ci).
Create pull request from completed feature branch using GitHub-native stacked PRs. Use when the user says 'create PR', 'submit for review', 'synthesize', or runs /synthesize. Validates branch readiness, creates PR with structured description, and manages merge queue. Do NOT use before review phase completes. Not for draft PRs.
Use when performing a first-pass, read-only PR review in a clean isolated context.
Turn a PR into tracked follow-up work — paste a PR or PR-comment link to extract the actionable ask and open a follow-up issue assigned to the @-mention or PR author; for a PR adding a design doc, it opens the missing `Implement:` tracking issue instead. Use for "make a follow-up issue", "create an issue for this", or a pasted PR/comment link with that intent.