pr-summary
Create a PR with dev as base using the pull request template. Use when opening a new PR.
Works with
--- name: pr-summary description: Create a PR with dev as base using the pull request template. Use when opening a new PR. license: MPL-2.0 --- Summarize the latest changes in this branch to create a pull request on GitHub. <workflow-steps> 1. Compare the current branch against default branch to see what changes need to be described in the pull request. Make sure to only focus on the finalized implementation details. Since pull requests tend to have work-in-progress commits at the beginning, you should be extra mindful on whether these are still relevant in the finalized snapshot. 2. Use the [pull request template](assets/pull-request-template.md) to generate a `.claude/scratchpad/PR.md`. 3. Pause here and prompt the user to check the `.claude/scratchpad/PR.md` before proceeding. 4. Once edited and approved by the user, fill in the missing details in the following script and then run it: ```bash gh pr create --base dev --head "$(git rev-parse --abbrev-ref HEAD)" --title '[TICKET-123] category: short title' --body-file .claude/scratchpad/PR.md ``` 5. Delete `.claude/scratchpad/PR.md` once successfully submitted. </workflow-steps>
More Code Review skills
pr-to-video
heygen-com/hyperframes
Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.
receiving-code-review
obra/superpowers
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
public-relations
coreyhaines31/marketingskills
When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' 'podcast prep,' 'going on a podcast,' 'podcast guest,' 'prep me for this podcast,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, prepping podcast appearances, and responding to press requests. For startup/SaaS/AI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.
