Borrowing it
Nothing to install: this file belongs to paulbreuler/limps. 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/paulbreuler/limps/main/.claude/commands/pr-create.mdgit clone --depth 1 https://github.com/paulbreuler/limpsWrote 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/paulbreuler/limps/pr-create)<a href="https://agentmods.dev/commands/paulbreuler/limps/pr-create"><img src="https://agentmods.dev/badge/commands/paulbreuler/limps/pr-create/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/paulbreuler/limps/pr-create"><img src="https://agentmods.dev/badge/commands/paulbreuler/limps/pr-create.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.00000 | $0.01384 |
| Opus 5.5 | $0.00000 | $0.00554 |
| Sonnet 5.5 | $0.00000 | $0.00277 |
| Haiku 4.5 | $0.00000 | $0.00138 |
Grade A, and why
pr-create 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Creation (limps)
Create a PR on GitHub with a limps-aware description based on staged changes or recent commits.
Instructions for Claude
When this command is invoked, you must:
-
Check prerequisites:
- Verify current branch is not
main - Check if branch is pushed (
git push --dry-run) - Verify GitHub CLI is available (
gh --version) - Check if PR already exists (
gh pr view)
- Verify current branch is not
-
Optional: Run code reviews (recommended before PR creation):
- Review order: Run reviews in parallel if possible, or sequentially (branch review first, then MCP review)
- For general code review: Invoke
/branch-code-reviewskill to review architecture, maintainability, and correctness - For MCP/LLM security review: Invoke
/mcp-code-reviewskill to review security, MCP safety, and LLM-related concerns - Timing: Run reviews after analyzing git changes (step 4) to have full context
- Include review findings in PR description if issues are found (or note that reviews passed)
-
Detect plan/agent context (if applicable):
- Use limps MCP tools when available:
list_plans,list_agents,get_plan_status,process_doc
- If a plan is inferred (via modified files under
plans/or commit messages), locate the agent file and extract:- Agent title, status, and feature list from frontmatter/sections
- If no plan/agent is detected, proceed as a standard PR.
- Use limps MCP tools when available:
-
Analyze git changes:
- Detect base branch:
- If user specifies base (e.g.,
--base develop), use that - Otherwise, detect default:
git symbolic-ref refs/remotes/origin/HEAD→ extract branch name - Fallback: try
origin/main, thenorigin/master - If no base branch found, ask user or default to
main
- If user specifies base (e.g.,
- Use
git log <base>..HEADandgit diff --stat <base>..HEAD - Edge case: If no commits exist (only staged changes), analyze
git diff --cachedinstead - Summarize key files and modules touched
- Detect base branch:
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 · 131 lines · 0 tokens per session scan A 3bac5819b268
pr-create is a command published in the GitHub repository paulbreuler/limps (10 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,384 tokens. 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 commands, from other repositories
fix-issues
Diagnose, reproduce, then fix reproducible open GitHub issues in parallel: one clean worktree/issue; symlink build artifacts to avoid rebuilds.
review-prs
Parallel PR triage: decide merge-worthiness, prepare rebased worktrees, fix blockers, return them for human merge.
release
Release all packages at specified version.
pr
A guided command for preparing a GitHub Pull Request, which is a proposed set of repository changes for review and merging. It reads the branch history and changed files to draft the request.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
clean_gone
Cleans up all git branches marked as [gone] (branches that have been deleted on the remote but still exist locally), including removing associated worktrees.