Borrowing it
Nothing to install: this file belongs to chrisgleissner/llm-tools. 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/chrisgleissner/llm-tools/main/.github/prompts/pr-converge.prompt.mdgit clone --depth 1 https://github.com/chrisgleissner/llm-toolsWrote 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/commands/chrisgleissner/llm-tools/pr-converge)<a href="https://agentmods.dev/commands/chrisgleissner/llm-tools/pr-converge"><img src="https://agentmods.dev/badge/commands/chrisgleissner/llm-tools/pr-converge/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/commands/chrisgleissner/llm-tools/pr-converge"><img src="https://agentmods.dev/badge/commands/chrisgleissner/llm-tools/pr-converge.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.00010 | $0.01033 |
| Opus 5.5 | $0.00004 | $0.00413 |
| Sonnet 5.5 | $0.00002 | $0.00207 |
| Haiku 4.5 | $0.00001 | $0.00103 |
Grade A, and why
pr-converge 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 26d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Convergence
Bring the current pull request to a merge-ready state.
This is an execution prompt, not an analysis prompt. Do not stop after identifying fixes, validation steps, or next actions. Carry the work through to completion unless genuinely blocked by missing permissions or an external outage.
This requires:
- Addressing all PR review comments.
- Ensuring all CI checks for the branch are green.
- Iterating until the pull request stabilizes.
- Pushing any required commits.
- Replying on and resolving every applicable review thread.
- Meeting repository coverage requirements.
Use the gh tool to interact with GitHub.
Convergence Loop
Work iteratively until all conditions are satisfied.
A PR is considered converged when:
- all review comments have been addressed
- all review threads are resolved
- all CI checks for the branch are passing
- the repository builds successfully
Continue iterating until this state is reached.
Do not end your run with phrases like:
- "Remaining gap"
- "Natural next steps"
- "I did not push"
- "I did not resolve threads"
If those items still remain, you are not done and must continue.
Step 1 — Review Comments
Using the gh tool:
- Retrieve all review comments on the pull request.
- Process each comment individually.
Default assumption:
Every comment is potentially valid.
For each comment:
- Read the comment and surrounding code.
- Investigate the concern raised.
- Determine whether the issue is:
- a real defect
- a valid improvement
- a misunderstanding
- already resolved
- no longer applicable
Step 2 — Implement Fixes
If the comment identifies a real issue:
- Implement the fix.
- Keep the fix minimal and focused.
- Follow repository coding standards.
- Add a regression test if the issue represents a bug.
After implementing the fix:
- respond to the review comment explaining the change
- resolve the thread using the gh tool
- if code changed, continue through validation, commit, push, and CI re-checks before stopping
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.
- 26d ago First seen · 217 lines · 10 tokens per session scan A 7808cc6de8cf
pr-converge is a command published in the GitHub repository chrisgleissner/llm-tools (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 10 tokens to every session and 1,033 once invoked, about $0.0000 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-10-03.
Other commands, from other repositories
review
Unified review orchestrator — detect changes, dispatch reviewers, validate findings, optionally post GitHub inline comments.
aitask-web-merge
Merge completed Claude Web branches to main and archive task data.
elegant-code-review
Review the current working diff against the elegant-code decision ladder and propose deletions, honoring the negligence floor.
prp-commit
Quick commit with natural language file targeting: describe what to commit in plain English.
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.
karpathy-check
Revisa as alterações em stage (ou o último commit) com base nos 4 princípios de codificação do Karpathy. Verifica complexidade, ruído no diff, suposições ocultas e verificação de objetivos. Uso: /karpathy-check [--last-commit].