agentleFS
anirudhaxeanirudhaxe/friday-skills/skills/html-pr-review/SKILL.md

html-pr-review

Skill0 starsChanged 5 months agoMITView on GitHub

Help review a PR by creating a single self-contained HTML artifact that renders the full diff with inline margin annotations, severity-coded findings, and structured review notes. Use when the user asks for a PR review, code review, diff analysis, or wants to understand changes in a pull request.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a comprehensive, visually rich PR review as a single self-contained HTML file.

    line 8
  2. Distinctive:

    Every PR review HTML must include these sections in order:

    line 16
  3. Distinctive:

    Use text + visual depictions

    line 30
  4. Distinctive:

    Use CSS-only expand/collapse for lengthy sections (no JS required for basic toggles, but JS is fine for interactive diffs)

    line 60
  5. Distinctive:

    Use git log for commit messages if helpful

    line 74

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

HTML PR Review

Create a comprehensive, visually rich PR review as a single self-contained HTML file. The review must make it easy to understand what changed, why, and what risks exist.

Output format

Write the output to a single .html file in the current working directory. Use a descriptive filename like pr-review-{branch-or-pr-number}.html. The HTML must be fully self-contained (CSS and JS inline, no external dependencies). Create the output in dark mode (adjust colors of the elements like text etc if needed for good dark mode visibility).

Structure

Every PR review HTML must include these sections in order:

1. Header

  • PR title, author, branch/source info
  • Total summary: files changed, insertions, deletions
  • Overall verdict badge (Looks Good / Needs Discussion / Changes Requested)

2. Summary

  • 2-3 sentence high-level description of what this PR does
  • Bullet list of key changes
  • 1-2 sentence risk assessment

3. Flow

  • Make the user understand the flow of the changes done in the PR
  • Use text + visual depictions

4. Severity-Coded Findings

A table of all findings with color coding:

  • 🔴 Critical (red) — Bugs, security issues, data loss
  • 🟡 Warning (yellow/amber) — Logic concerns, performance, edge cases
  • 🔵 Suggestion (blue) — Style, readability, best practices
  • ⚪ Praise (gray) — Well-done sections worth highlighting

Each finding row: finding ID | severity | file:line | description | recommendation

5. File-by-File Diff with Annotations

For each changed file:

  • File path header with change stats (++,--)
  • Render the full diff with:
    • Line numbers on the left
    • Removed lines in red background with - prefix
    • Added lines in green background with + prefix
    • Unchanged context lines in neutral background
    • Inline margin annotations — numbered callouts in the left margin that map to findings in the previous section
  • Collapse very large unchanged sections (>5 lines) with a click-to-expand

6. Discussion Points

  • Open questions or areas needing author clarification
  • Specific line references

Style guidelines

  • System-ui font stack, max-width 960px centered
  • Diff rendering: monospace font, side-by-side or unified (prefer unified with line numbers)
  • Use CSS-only expand/collapse for lengthy sections (no JS required for basic toggles, but JS is fine for interactive diffs)
  • Color palette:
    • Added: #e6ffec background, #216e39 text
    • Removed: #ffebe9 background, #cf222e text
    • Critical: #cf222e
    • Warning: #bf8700
    • Suggestion: #0969da
    • Praise: #656d76
  • Responsive: readable on both desktop and mobile

Data sources

  • Get the diff via git diff main...HEAD or git diff {base}...{head}
  • Get PR metadata via gh pr view {number} if applicable
  • Use git log for commit messages if helpful

After writing

End your response with: Review created: {filename} — providing a relative path to the HTML file.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.