Rsdoctor is a build analyzer for Rspack projects that shows how compilation works, what it produces, and where build problems occur. Development teams use it to inspect build artifacts and timing, check build rules, and add custom scans. The catalogue add-ons provide ways to work with Rsdoctor.
Borrowing it
Nothing to install: this file belongs to web-infra-dev/rsdoctor. 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/web-infra-dev/rsdoctor/main/.agents/skills/pr-creator/SKILL.mdgit clone --depth 1 https://github.com/web-infra-dev/rsdoctorWrote 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/web-infra-dev/rsdoctor/pr-creator)<a href="https://agentmods.dev/skills/web-infra-dev/rsdoctor/pr-creator"><img src="https://agentmods.dev/badge/skills/web-infra-dev/rsdoctor/pr-creator/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/web-infra-dev/rsdoctor/pr-creator"><img src="https://agentmods.dev/badge/skills/web-infra-dev/rsdoctor/pr-creator.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.00023 | $0.00484 |
| Opus 5.5 | $0.00009 | $0.00194 |
| Sonnet 5.5 | $0.00005 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
pr-creator 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- pr-creator — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull request creator
Steps
-
Confirm the current branch with
git branch --show-current. If it is the default branch, create and switch to a new branch before doing anything else. Use a descriptive branch name, preferablyfeat-<topic>orfix-<topic>. -
Review local changes with
git status --short. Do not revert unrelated user changes. Before creating the PR, ensure the intended changes are committed and never commit directly on the default branch. -
Read the repository's PR template when available and follow its current headings and guidance.
-
Draft the PR title in the repository's standard format. If the repository uses Conventional Commits, common patterns include:
feat(core): add ...fix(types): ...docs: ...refactor(types): ...chore(ci): ...for CI workflow, check, or release automation changeschore(deps): ...release: v1.2.0
-
Write the PR body in concise, clear English.
- Explain the problem or motivation and why it matters, then describe the approach and resulting behavior.
- Include API, compatibility, or migration details when they help reviewers assess the change.
- Keep typical descriptions to a few short sentences. Focus on the key changes rather than a file-by-file summary.
- Include tests, documentation, and validation required by repository guidelines or the template. Otherwise, mention them only when central to the change or relevant to review risk.
-
Include relevant issue, discussion, or design links alongside the context they support, following the template's guidance. For dependency upgrades, link to the target version's release notes or tag when available.
-
Push the branch only after re-checking the branch name. Never push the default branch directly.
-
Create the PR. When running in Codex, use the Codex GitHub connector/plugin for GitHub operations. Use
gh pr createonly as a fallback when the connector is unavailable.
Constraints
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 Changed 7545309b5b4a
- 1mo ago Changed · -8 lines · -18 tokens per session 0297d9d9f685
- 2mo ago First seen · 57 lines · 41 tokens per session scan A fdb78d1ef2dd
pr-creator is a skill published in the GitHub repository web-infra-dev/rsdoctor (1,151 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 484 once invoked, about $0.0001 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
repository-assisted-apply
Safely review, apply, verify, activate, and record one user-selected object in an ABAP FS Copilot-assisted repository-comparison workflow. Use only after the repository workflow has a prepared assisted-apply plan and the user has enabled Copilot-assisted apply.
oss-submit-pr
Submit a pull request following the repo's contribution guidelines. Reviews the diff, checks for common rejection reasons, and helps the user write their own PR description. The LLM reviews. the user writes. Use when implementation is complete and tests pass. Not for responding to review comments after the PR is open.…
oss-post-pr
Handle PR review feedback - understand reviewer comments, research their concerns, and help the user address them. The LLM explains what reviewers want and why; the user decides how to respond and writes the code. Use when you receive review comments on a submitted PR. Not for opening the PR in the first place, which…
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.