agentmods.dev

ai-diff-reviewer-open-pr

A skill that reads a code branch’s changes and writes a GitHub pull request title and description.

In plain words
What is it for?
Use it to prepare a pull request from the current branch, including repository-specific sections and a preview before the remote PR is updated.
Why use it?
It gives reviewers a clear summary, test instructions, and relevant notes about UI or API changes.

Skill for Claude CodeCodex

20 1mo ago D scan 207 tokens original MIT
View the source file DailybotHQ/deepworkplan-skill
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/dailybothq/deepworkplan-skill/open-pr
Any agent
npx skills add DailybotHQ/deepworkplan-skill --skill open-pr
Clone the repo
git clone --depth 1 https://github.com/DailybotHQ/deepworkplan-skill

Made for: Claude Code, Codex.

Per session 207 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 9,921 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00207 $0.09921
Opus 5 $0.00103 $0.04960
Sonnet 5 $0.00041 $0.01984
Haiku 4.5 $0.00021 $0.00992

Measured 3d ago against content hash 5094ff9d9d5c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade D, and why

ai-diff-reviewer-open-pr scanned grade D with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

| `<!-- HTML comment instructions -->` | *(no equivalent)* | Stripped from the final body. Instructions are for the author, not the reviewer. |

Strips warnings and disclaimersmediumAnti-refusal

Omitting safety caveats hides risk from the user and is a common jailbreak preamble.

- Run `docs-site build`; confirm the new page renders without warnings
.agents/skills/ai-diff-reviewer/open-pr/SKILL.md · 926 lines

How it starts

The opening of the file, as written. The whole thing — 926 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AI Diff Reviewer — Open PR (sub-skill)

Companion to the ai-diff-reviewer skill. Where the parent reviews the current branch's diff locally, this sub-skill takes the next logical step: authors a well-documented pull request from the same diff — title, body, and (on request) a draft opener.

The design philosophy is unopinionated where it can be, opinionated where it needs to be:

  • Unopinionated: the section shape adapts to your .github/pull_request_template.md when one exists. If your team already writes PRs with ## Rollout plan and a ## Security review checkbox, those survive intact.
  • Opinionated: every PR gets a Summary that leads with the outcome, a Test plan a reviewer can actually run, and — when the diff signals it — a Screenshots prompt for UI changes and a Breaking changes callout for API changes. These are the sections whose absence reviewers complain about; the skill won't let them slip.

Nothing gets pushed. Nothing gets merged. The skill only ever writes the PR title + body on the remote via gh, always after a single-yes preview.

When it fires

Create a fresh PR — triggers:

  • "Open the PR", "open a pull request for this branch"
  • "Create the PR", "create a pull request"
  • "Draft the PR title and description"
  • "I'm ready to push this for review — write the PR"
  • "Make a draft PR" (adds --draft)

Refresh / fix an existing PR — triggers:

  • "Update the PR description"
  • "The PR body is a one-liner — rewrite it in the proper format"
  • "Fix the PR title, it doesn't match the diff anymore"
  • "Refresh the PR body — I pushed new commits"

Fall through to a sibling skill when the developer:

  • Wants a local review before pushing → parent ai-diff-reviewer skill (default review flow). This sub-skill is the natural next step after that review.
  • Wants to install the CI action → setup.
  • Wants to customize the review → generate-extension.
  • Wants a git commit message (not a PR body) → defer; this skill writes PRs, not individual commits.

Read the full file on GitHub · 926 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 926 lines · 207 tokens per session scan D 5094ff9d9d5c

Subscribe to this mod's changes

ai-diff-reviewer-open-pr is a skill published in the GitHub repository DailybotHQ/deepworkplan-skill (20 stars, last pushed 1mo ago), licensed MIT. It adds 207 tokens to every session and 9,921 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it D with 2 findings (hidden instructions, strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code reviewGit and workflow
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens