Borrowing it
Nothing to install: this file belongs to vlad-ryzhkov/ai-context-engineering-for-qa. 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/vlad-ryzhkov/ai-context-engineering-for-qa/main/.claude/skills/pr/SKILL.mdgit clone --depth 1 https://github.com/vlad-ryzhkov/ai-context-engineering-for-qaWrote 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/vlad-ryzhkov/ai-context-engineering-for-qa/pr)<a href="https://agentmods.dev/skills/vlad-ryzhkov/ai-context-engineering-for-qa/pr"><img src="https://agentmods.dev/badge/skills/vlad-ryzhkov/ai-context-engineering-for-qa/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/vlad-ryzhkov/ai-context-engineering-for-qa/pr"><img src="https://agentmods.dev/badge/skills/vlad-ryzhkov/ai-context-engineering-for-qa/pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00045 | $0.00574 |
| Opus 5 | $0.00023 | $0.00287 |
| Sonnet 5 | $0.00009 | $0.00115 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
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 today.
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.
What it actually says
/pr — Pull Request Creator
Execution: Output only the final result and PR URL. Suppress intermediate command output unless an error blocks the PR.
When to Use
- All planned changes are implemented and locally verified
- Ready to submit work for code review
- Branch does not yet exist on remote
Steps
1. Confirm Target Branch
Ask the user for the target branch (never assume main vs master).
2. Run Quality Gates
./scripts/pre-push.sh
Stop and report failures before proceeding.
3. Commit Changes
Stage relevant files (not .env, secrets, or build output). Commit with conventional commit format:
<type>: <description in English>
Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
Types: feat, fix, test, chore, docs, refactor
4. Push Branch
git push -u origin <branch-name>
5. Create PR
PR title: conventional commits format, Latin only, under 70 characters.
PR body: summarize changes in English. Include test coverage note if applicable.
gh pr create --title "<type>: <description>" --body "$(cat <<'EOF'
## Summary
- <bullet 1>
- <bullet 2>
## Test plan
- [ ] compileTestKotlin passes
- [ ] ktlintCheck passes
- [ ] Tests cover the changed scenario
🤖 Generated with Claude Code
EOF
)"
Quality Gates
-
./scripts/pre-push.sh→ all checks passed - PR title: conventional commits, Latin only (CI enforced)
Self-Review Checklist
Before creating the PR:
- All planned changes are staged and locally committed
- Branch is up to date with remote base branch
- Pre-push hook passes without errors
Gardener: If you notice rule drift or improvements during this run, briefly note it here.
Rules
- Never push without confirming target branch name with the user
- Never skip
./scripts/pre-push.sh— broken code must not reach PR - Never use
--no-verifyor--forcewithout explicit user instruction
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.
- today Changed · +66 lines · +26 tokens per session 22c145489370
- 9d ago First seen · 25 lines · 19 tokens per session scan A c84a4ba54bcc
pr is a skill published in the GitHub repository vlad-ryzhkov/ai-context-engineering-for-qa (6 stars, last pushed today), licensed Unlicense. It adds 45 tokens to every session and 574 once invoked, about $0.0002 per session on Opus 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-31.
Other skills, from other repositories
hyperflow-audit
Hyperflow code review. Use when the user wants the current diff, a commit, branch, or PR reviewed — verbs like audit, review, "check for issues", "security check", "code review". Multi-level review (L1 quick → L5 exhaustive), writes findings to .hyperflow/audits/, then a fix-gate.
code-review-github
GitHub PR workflow orchestration for code review — list PRs, post comments, apply labels, and guarded auto-merge.
plugin-code-review-orchestrated
Orchestrates a code review of the spring-plugin repository through scope/context passes, routing, domain reviewer subskills, and per-artifact validation. Use when asked to review a PR, diff, commit, branch, module, or file set, to run a full orchestrated review, or to produce a validated review report.
release-new-version
Use when the user wants to release a new Zafiro version — drafting bilingual release notes, deciding the next version number, bumping app/build.gradle.kts, tagging, and publishing to GitHub (main repo, optionally the Xposed repo).
review-scope-resolver
Normalizes a PR, diff, commit, branch, file list, directory, module, class, or function into an exact review target with semantic clusters and routing signals for domain reviewer subskills. Use as the first pass of an orchestrated code review, when asked to resolve review scope, or when a raw review reference must be…
05-review
Review a diff read-only on three axes, code, behavior versus the plan, and relevancy, into one verdict report. Use before shipping a change. Not for fixing findings or auditing a codebase.