Prepare or update AUV pull requests with source-backed CLI, Protobuf/Runner, and public API change disclosures, before-and-after usage, and migration notes. Also use for retrospective API audits of specified PRs or revisions.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Create PR
Make the PR useful to both reviewers and downstream callers. Explain the final
behavior, show exact calling changes, and preserve enough source context to audit
those claims later. Follow the repository's AGENTS.md and PR template.
## Establish the comparison
- Identify the repository, PR or branch, base, and head. Record resolved commit
SHAs in the disclosure. Use the actual PR diff, not every change since `main`.
- For an open PR, compare its merge base with its head. For a merged or historical
change, identify the reviewed or landed revision range and state which one you
used. Do not infer historical behavior from today's working tree. A commit in
Git is not proof of merge or release; use “head revision” unless that status
was verified.
- For stacked PRs, distinguish changes introduced here from changes inherited
from the base. State dependencies and merge order. Recheck the base after an
upstream merge; do not claim independence merely because a PR has its own URL.
- Start with changed files, then inspect definitions, exports, and real callers
at both revisions. Use `git show`, `git diff`, and targeted `rg` searches.
…
The line at the top of this page pins the label git:20261004.a5ef613, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_dqrvxxrrv4qfohxd
GET https://markdownregistry.com/api/v1/resolve?ref=moeru-ai/auv/create-pr
GET https://markdownregistry.com/api/v1/blob/be3d85239b125f6d4c67685fb4919d26f5170ff8970837550a9242e2b304ff8a
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
moeru-ai/auv · .agents/skills/ast-grep/SKILL.md · Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search…
moeru-ai/auv · .agents/skills/auv-wayland-rendering/SKILL.md · Prepare, diagnose, and validate Linux GPU and Wayland environments for AUV rendering and capture through XDG Desktop…
moeru-ai/auv · .agents/skills/domain-web/SKILL.md · Use when building web services. Keywords: web server, HTTP, REST API, GraphQL, WebSocket, axum, actix, warp, rocket…
fcakyon/claude-codex-settings · plugins/github-dev/skills/create-pr/SKILL.md · This skill should be used when user asks to "create a PR", "make a pull request", "open PR for this branch", "submit…
block/berd · .agents/skills/create-pr/SKILL.md · Create a GitHub PR from the current branch: handle uncommitted changes, generate a summary, submit via gh CLI, then…
reflexioai/claude-smart · .agents/skills/create-pr/SKILL.md · Create high-quality pull requests via gh pr create. Use when the user wants to create a PR, submit a PR, open a pull…
tobihagemann/turbo · claude/skills/create-pr/SKILL.md · Create a GitHub pull request with a drafted title and description. Use when the user asks to "create a PR", "create a…
tobihagemann/turbo · codex/skills/create-pr/SKILL.md · Create a GitHub pull request with a drafted title and description. Use when the user asks to "create a PR", "create a…