pr-writing-review
Extract and analyze writing improvements from GitHub PR review comments. Use when asked to show review feedback, style changes, or editorial improvements from a GitHub pull request URL. Handles both explicit suggestions and plain text feedback. Produces structured output comparing original phrasing with reviewer suggestions to help refine future writing.
npx skills add evalstate/fast-agent --skill pr-writing-review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PR Writing Review Extract editorial feedback from GitHub PRs to learn from review improvements. ## Prerequisites - **GitHub CLI**: `gh` installed - **Authenticated `gh` session**: `gh auth status` should show you’re logged in - For private repos, your token needs appropriate scopes (typically `repo`). - **Python**: 3.12+ - **uv** (recommended): https://github.com/astral-sh/uv ## Division of Labor | Tool | Responsibility | | ----------------- | ----------------------------------------------------------------------- | | **Python script** | API calls, parsing, file tracking across renames, structured extraction | | **LLM analysis** | Pattern recognition, paragraph comparison, style lesson synthesis | ## Quick Start ```bash > **All paths are relative to the directory containing this SKILL.md file.** > Before running any script, first `cd` to that directory or use the full path. # Get suggestions and feedback uv run scripts/extract_pr_reviews.py <pr_url> # Get full first→final comparison for deep analysis uv run scripts/extract_pr_reviews.py <pr_url> --diff # Same as above, but cap each FIRST/FINAL dump to 2k chars for LLM prompting uv run scripts/extract_pr_reviews.py <pr_url> --diff
- Prerequisites
- Division of Labor
- Quick Start
- Workflow
- Step 1: Extract with --diff
- Step 2: Analyze the Output
- Script Options
- Output Structure
- Default Output
- With --diff
- Handling File Renames
- Example Analysis Output
- Limitations
Before running any script, first `cd` to that directory or use the full path. Get suggestions and feedback uv run scripts/extract_pr_reviews.py <pr_url> Get full first→final comparison for deep analysis uv run scripts/extract_pr_reviews.py <pr_url> --diff Same as above, but cap each FIRST/FINAL dump to 2k chars for LLM prompting uv run scripts/extract_pr_reviews.py <pr_url> --diff --max-file-chars 2000 uv run scripts/extract_pr_reviews.py https://github.com/org/repo/pull/123 --diff
What does the pr-writing-review skill do?
Extract and analyze writing improvements from GitHub PR review comments. Use when asked to show review feedback, style changes, or editorial improvements from a GitHub pull request URL. Handles both explicit suggestions and plain text feedback. Produces structured output comparing original phrasing with reviewer suggestions to help refine future writing.
How do I install it?
Run `npx skills add evalstate/fast-agent --skill pr-writing-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From evalstate/fast-agent, a repository with 3,880 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
