agentmods.dev

limps: Command for Claude Code

.claude/commands/pr-check-and-fix.md

pr-check-and-fix is a command for Claude Code from paulbreuler/limps. It costs 0 tokens per session (631 once invoked), scanned A, original, MIT.

A command for investigating failed pull-request checks and applying fixes through the repository's prescribed workflows. A pull request is a proposed code change waiting to be reviewed and merged.

In plain words
What is it for?
Use it to inspect failed checks, run the smallest relevant local command, make focused fixes, and rerun validation.
Why use it?
It organizes failures such as formatting, linting, type checks, builds, and tests, so you can reproduce and fix them systematically.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is paulbreuler/limps's own configuration. It tells Claude Code how to work on limps itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything limps configures →

not rated 10repo 6mo ago A scan 0 tokens original MIT
View source ↗ paulbreuler/limps basestate.io
Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/paulbreuler/limps/main/.claude/commands/pr-check-and-fix.md
Clone the repo
git clone --depth 1 https://github.com/paulbreuler/limps

Made for: Claude Code.

Wrote 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.

agentmods badge for pr-check-and-fix

README.md
[![agentmods](https://agentmods.dev/badge/commands/paulbreuler/limps/pr-check-and-fix.svg)](https://agentmods.dev/commands/paulbreuler/limps/pr-check-and-fix)
Your own site
<a href="https://agentmods.dev/commands/paulbreuler/limps/pr-check-and-fix"><img src="https://agentmods.dev/badge/commands/paulbreuler/limps/pr-check-and-fix.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 631 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00631
Opus 5 $0.00000 $0.00316
Sonnet 5 $0.00000 $0.00126
Haiku 4.5 $0.00000 $0.00063

Measured 7d ago against content hash 35d9873f61e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

pr-check-and-fix 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 7d 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.

.claude/commands/pr-check-and-fix.md · 57 lines

How it starts

The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PR Check and Fix (limps)

Triage failing PR checks and apply fixes using limps workflows and scripts only.

Instructions for Claude

When this command is invoked, you must:

  1. Resolve PR context:

    • gh pr view --json number,title,url,headRefName,baseRefName,statusCheckRollup
    • If no PR exists, report and stop

  2. Summarize check status:

    • List failed checks with URLs
    • Separate by category: format, lint, type-check, build, test

  3. Reproduce locally:

    • Run the minimal failing command first
    • Use repo scripts only:
      • Root: npm run format:check, npm run lint, npm run type-check, npm run build, npm test
      • Workspaces: npm test --workspace <name> etc.

  4. Fix iteratively:

    • Apply code changes narrowly
    • Re-run the failing command
    • Then run full validation: npm test (or npm run validate if requested)

  5. Optional: Run code reviews after fixes:

    • When to review: Run reviews if fixes involve:
      • Security-related changes (always review with /mcp-code-review)
      • Architecture changes (multiple files, new patterns)
      • Complex logic changes (not just formatting/linting)
      • Changes to MCP tools/resources or RLM sandbox
    • Review timing: After all fixes are complete, before final commit
    • Invoke /branch-code-review for architecture/maintainability concerns
    • Invoke /mcp-code-review for security/MCP/LLM concerns
    • If reviews find new issues, fix them before committing

  6. Commit and push fixes:

    • Commit message format: Use conventional commits, reference the failing check:
      • fix(ci): resolve linting errors in server.ts
      • fix(test): update test assertions for new API
      • fix(format): apply prettier formatting
    • Use /git-commit-best-practices for detailed commit message guidance
    • Commit scope: Reference the package/component that was fixed
    • Push branch: git push (force push only if rebased: git push --force-with-lease)
    • Re-check PR status: gh pr checks or view PR in browser

Read the full file on GitHub · 57 lines

Changes

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.

  1. 7d ago First seen · 57 lines · 0 tokens per session scan A 35d9873f61e8

Subscribe to this mod's changes

pr-check-and-fix is a command published in the GitHub repository paulbreuler/limps (10 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 631 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.

DebuggingLLMai-agentsai-planningai-testing-best-practicesclicli-tool
Related

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.

can1357/oh-my-pi · 0 tokens

debug

A command for investigating software errors by classifying them, tracing their source, and comparing expected with actual behaviour.

echoVic/blade-code · 5 tokens

fire-resurrect

Autonomous Resurrection Mode — reverse-engineer intent from messy code, then rebuild clean from scratch.

ThierryN/fire-flow · 18 tokens

fire-verify-uat

Conversational User Acceptance Testing with automatic parallel diagnosis on failures.

ThierryN/fire-flow · 11 tokens

fix

⚡⚡ Analyze and fix small issues [AUTO DETECT COMPLEXITY].

ihatesea69/kiro-kit · 17 tokens

modernize-transform

Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.

ronmkr/PromptBook · 17 tokens