Borrowing it
Nothing to install: this file belongs to lukascivil/json-difference. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lukascivil/json-difference/master/.claude/skills/create-or-update-pr/SKILL.mdgit clone --depth 1 https://github.com/lukascivil/json-differenceWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/lukascivil/json-difference/create-or-update-pr)<a href="https://agentmods.dev/skills/lukascivil/json-difference/create-or-update-pr"><img src="https://agentmods.dev/badge/skills/lukascivil/json-difference/create-or-update-pr/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/lukascivil/json-difference/create-or-update-pr"><img src="https://agentmods.dev/badge/skills/lukascivil/json-difference/create-or-update-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00107 | $0.01965 |
| Opus 5.5 | $0.00043 | $0.00786 |
| Sonnet 5.5 | $0.00021 | $0.00393 |
| Haiku 4.5 | $0.00011 | $0.00197 |
Grade A, and why
create-or-update-pr scanned grade A with 0 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 1mo 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create or Update Pull Request
This skill creates a new PR for the current branch, or updates the existing PR if one is already open. In both cases, it regenerates the title (Conventional Commits) and body (Objective + What was done) from the actual diff and commit history. All output is in English, regardless of the conversation language.
When to use
Invoke this skill whenever the user wants to:
- Open a PR for the current branch
- Update an existing PR's title or description
- Refresh the PR after new commits on the branch
Do not invoke for: merging, reviewing, closing PRs, or operations against a different branch.
Preconditions
Before doing any network action, verify:
- The repository has a GitHub remote (
git remote -vshows github.com). If not, abort and tell the user. - The current branch is not the main/master branch. Detect the main branch with
gh repo view --json defaultBranchRef -q .defaultBranchRef.name. If the user is on it, abort and ask them to switch. - The
ghCLI is authenticated (gh auth status). If not, abort with instructions. - There are commits on the current branch beyond the merge base with the default branch. If zero commits ahead, abort — nothing to PR.
Steps
1. Gather branch + repo context (parallel)
Run these commands in parallel:
git branch --show-current # current branch
gh repo view --json defaultBranchRef -q .defaultBranchRef.name # default/base branch
gh pr list --head "<current-branch>" --state open --json number,title,body,url --limit 1
git status --porcelain # uncommitted changes check
git rev-parse --abbrev-ref "<current-branch>@{upstream}" 2>&1 # is branch pushed?
2. Gather change context (parallel)
Using the base branch discovered above:
git log <base>..HEAD --oneline # commit list
git diff <base>...HEAD --stat # files changed + insertions/deletions
git diff <base>...HEAD # full diff (truncate if huge)
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.
- 1mo ago First seen · 198 lines · 107 tokens per session scan A 668ccd69f957
create-or-update-pr is a skill published in the GitHub repository lukascivil/json-difference (58 stars, last pushed 2mo ago), licensed MIT. It adds 107 tokens to every session and 1,965 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
prettier-docs
Prettier 3.9.5 — opinionated code formatter. CLI, API, config, plugins, editor integration, CI.
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…
publish-npm-version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…
triage-contributor-pr
Triage open pull requests from external contributors to prisma/orm and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…
contrib-pr
Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.