review-pull
Review Gitea/Forgejo pull requests — checkout, approve, reject, request reviewers, inline comments, and diff/patch/files.
Works with
--- name: review-pull description: Review Gitea/Forgejo pull requests — checkout, approve, reject, request reviewers, inline comments, and diff/patch/files. license: MIT --- # Review Pull Request Prefer `tea pulls` commands for review workflows. Bundled actions are only for CLI gaps and are documented under `actions/pull-requests/README.md`. When resolving `actions/...` paths, use the `actions/` directory bundled relative to this skill directory. Pass explicit scope flags (`--login`, `--remote`, or `--repo`) to bundled actions when the user names a login, remote, backend, or repository. Otherwise, bundled actions use active-host-first discovery. ## Checkout and Review ```bash tea pulls checkout 15 # checkout PR locally tea pulls review 15 # interactive review tea pulls approve 15 # approve tea pulls reject 15 # request changes ``` ## Request Reviewers ```bash tea pulls edit 15 --add-reviewers user1,user2 tea pulls edit 15 --remove-reviewers user1 ``` ## Diff / Patch / Review Comments ```bash tea pulls 15 --fields diff,patch tea pulls review-comments 15 tea pulls resolve 123 tea pulls unresolve 123 ``` ## Forks and Upstream PRs See [pull-request-forks](pull-request-forks.md). For interactive inline review, use: ```bash tea pulls review 15 ``` ## Review Checklist Pattern ```bash tea pulls checkout 15 # ... test locally ... tea pulls approve 15 tea pulls merge 15 --style squash tea pulls clean 15 ``` ## Tips - `tea pulls checkout` creates a local tracking branch
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.
