New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Review Follow Up

by Porabuild in Porabuild/Poracode

Work through pull request review feedback: sort what is actionable, fix it, and reply accurately.

Apache-2.0Auto-check passedDevelopment

Install Review Follow Up

skills CLI
$ npx skills add Porabuild/Poracode --skill review-follow-up -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Porabuild/Poracode review-follow-up --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Porabuild/Poracode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/plugins/github/skills/review-follow-up .claude/skills/review-follow-up && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
review-follow-up
GitHub stars
115
Token cost
~453 tokens
SKILL.md length
270 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
Apache-2.0

At a glance

Work through pull request review feedback: sort what is actionable, fix it, and reply accurately.

  • Tasks that involve Pull requests
  • SKILL.md covers Collect the feedback, Work the actionable ones, Reply and Report
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Review Follow Up is an agent skill from Porabuild/Poracode. Work through pull request review feedback: sort what is actionable, fix it, and reply accurately.

Its SKILL.md is about 450 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. The repository describes itself as: One window for all your AI coding agents. Run Claude, Codex, OpenCode, Gemini, Antigravity, Cursor, and Copilot side-by-side. Terminal and chat, any layout. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/review-follow-up”

What it can do on your machine

Read from SKILL.md and the folder at commit e56fcc8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Review Follow Up loads about 453 tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 270 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~29
When it runs · the whole SKILL.md, loaded when a task matches
~453

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Porabuild/Poracode at commit e56fcc8, republished under its Apache-2.0 licence (© Porabuild). 270 words, ~453 tokens.

Download SKILL.mdSave it as .claude/skills/review-follow-up/SKILL.md (or your agent's skills folder).
name
review-follow-up
description
Work through pull request review feedback: sort what is actionable, fix it, and reply accurately.

Review Follow-up

Turn review comments on a pull request into landed changes.

Collect the feedback

Read every review thread, not just the top-level review summaries. Include threads marked resolved only if the user asks — a resolved thread usually means it is already handled.

Sort each comment into one of three buckets and say which is which:

  • Actionable — a concrete change is being requested.
  • Question — the reviewer wants an explanation, not a diff.
  • Note — an observation with no change implied.

Work the actionable ones

Fix them in the code, not in the reply. Group related comments so you make one coherent change rather than several overlapping ones.

If you disagree with a comment, say so to the user with your reasoning and let them decide. Do not silently skip it, and do not implement something you believe is wrong without flagging it.

If a comment is ambiguous enough that two readings lead to different code, ask rather than guess.

Reply

Reply once per thread, after the change exists. State what you changed and where. Do not claim a comment is addressed until the code is actually written.

Replies are outward-facing: show the user the text before posting.

Before posting, re-read the thread and the current diff so the reply describes the change that actually exists. After posting, verify the reply is attached to the intended thread; do not resolve a thread unless the user requested it.

Report

List what you changed, what you answered without changing, and what you deliberately left — with the reason. If some feedback is still open, say that plainly instead of implying the review is fully handled.

© Porabuild, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in resources/plugins/github/skills/review-follow-up of Porabuild/Poracode.

Open the folder on GitHubat commit e56fcc8

Compare with similar skills

Review Follow Up next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Review Follow Up compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Review Follow Up this skillPorabuild/Poracode115—~453Automated safety check: PassApache-2.0
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands91k—~2.4kAutomated safety check: PassMIT
WooCommerce Code Reviewwoocommerce/woocommerce11k3 repos~1.1kAutomated safety check: PassCustom licence

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    91k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Record PR Demo

    payloadcms/payload

    A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.

    45k GitHub stars~1k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from Porabuild/Poracode

All 21 skills in this repo

  • Interactive Testing

    Porabuild/Poracode

    Run repeatable integration and smoke testing against the real Poracode Electron app through Chrome DevTools Protocol.

    115 GitHub stars~4.5k tokensUpdated today
    Auto-check: notes

  • Release Notes

    Porabuild/Poracode

    Write consistent, hand-written-looking changelog entries for a Poracode release.

    115 GitHub stars~4.2k tokensUpdated today
    Auto-check passed

  • Skill Creator Poracode

    Porabuild/Poracode

    Create a new reusable agent skill managed by Poracode. An agent skill from Porabuild/Poracode.

    115 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • App Controls

    Porabuild/Poracode

    Inspect and drive Poracode itself — the Terminal panel, other threads, projects, workspaces, git, pull requests, and schedules — through the poracode MCP.

    115 GitHub stars~745 tokensUpdated today
    Auto-check passed

  • Chrome Control

    Porabuild/Poracode

    Use the user's real Chrome tabs and signed-in sessions for visible browser workflows.

    115 GitHub stars~691 tokensUpdated today
    Auto-check passed

  • Computer Use

    Porabuild/Poracode

    Inspect and operate native Windows, macOS, or Linux applications through Poracode's desktop-control tools.

    115 GitHub stars~718 tokensUpdated today
    Auto-check passed

Categories

Questions about Review Follow Up

What does Review Follow Up do?

Work through pull request review feedback: sort what is actionable, fix it, and reply accurately. Review Follow Up is an agent skill from Porabuild/Poracode. Work through pull request review feedback: sort what is actionable, fix it, and reply accurately.

When should I use Review Follow Up?

Review Follow Up fits situations like: tasks that involve Pull requests.

How do I install Review Follow Up in Claude Code?

Run `npx skills add Porabuild/Poracode --skill review-follow-up -a claude-code`. Or copy the skill folder (resources/plugins/github/skills/review-follow-up in Porabuild/Poracode) into .claude/skills/review-follow-up in your project. Claude Code loads it when a task matches its description.

How do I install Review Follow Up in Codex?

Run `npx skills add Porabuild/Poracode --skill review-follow-up -a codex`. Or copy the skill folder (resources/plugins/github/skills/review-follow-up in Porabuild/Poracode) into .agents/skills/review-follow-up in your project. Codex loads it when a task matches its description.

Can I use Review Follow Up in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Porabuild/Poracode --skill review-follow-up -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-follow-up, .gemini/skills/review-follow-up, .github/skills/review-follow-up and .opencode/skills/review-follow-up in your project.

What does Review Follow Up need to run?

SKILL.md names no scripts, command-line tools or credentials: Review Follow Up is instructions for the agent only.

Does Review Follow Up access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Review Follow Up safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Review Follow Up use?

Review Follow Up is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Review Follow Up use?

About 453 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Review Follow Up?

Skills that share tags, products or a category with Review Follow Up: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 91k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Review Follow Up?

Porabuild (a GitHub organization) maintains it in Porabuild/Poracode, which has 115 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 10, 2026.

Source: Porabuild/Poracode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.