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/skills/branch-code-review/SKILL.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/skills/paulbreuler/limps/branch-code-review)<a href="https://agentmods.dev/skills/paulbreuler/limps/branch-code-review"><img src="https://agentmods.dev/badge/skills/paulbreuler/limps/branch-code-review/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/paulbreuler/limps/branch-code-review"><img src="https://agentmods.dev/badge/skills/paulbreuler/limps/branch-code-review.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.00030 | $0.00656 |
| Opus 5.5 | $0.00012 | $0.00262 |
| Sonnet 5.5 | $0.00006 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
branch-code-review 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Branch Code Review (General)
Purpose
Perform a general code review on the current branch compared to the base branch (main by default), focusing on architecture, maintainability, and correctness.
Scope
- If
$ARGUMENTSis provided, treat it as a scope (paths, diff range, or PR number). - If no arguments are provided, review
base...HEADwherebaseis detected (origin/main→origin/masterfallback).
Workflow
- Determine diff target
- Detect base branch:
git symbolic-ref refs/remotes/origin/HEAD→ extractmainormaster.- If not available, try
origin/main, thenorigin/master.
- Detect base branch:
- Enumerate change surface
git diff --name-status base...HEADgit log --oneline base...HEAD- Read the diff before diving into code.
- Architecture pass
- Evaluate loose coupling, high cohesion, extensibility, and DRY.
- Check module boundaries and whether responsibilities are clearly separated.
- Maintainability pass
- Keep files under ~500 lines unless necessary.
- Names are descriptive; public names are concise; internal names can be verbose.
- Comments explain why for non-obvious logic; remove redundant comments.
- Documentation is updated for behavior, usage, or interface changes.
- Correctness and safety
- Validate logic, edge cases, and error handling.
- Look for regressions, config mismatches, or hidden coupling.
- Tests
- Ensure tests exist and are meaningful for the change surface.
- Prefer tests that would fail on broken behavior.
Best-Practice Signals (from authoritative guidance)
- Review design and interactions first; validate overall intent. (Google Eng Practices)
- Read every changed line in logical sequence; expand context if needed. (Google + Microsoft)
- Focus on correctness, readability/maintainability, and test quality. (Microsoft)
- Use structured checklists to avoid missing issues. (Atlassian)
Repo-Specific Context
This repo is evolving toward extensible planning/content management. Favor:
- Clear interfaces for future content types beyond plans.
- Minimal cross-package coupling.
- Extensible, composable APIs (avoid one-off branching).
- Config/format stability to support long-lived plans and migrations.
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 · 73 lines · 30 tokens per session scan A a4d40e7d6e6a
branch-code-review is a skill published in the GitHub repository paulbreuler/limps (10 stars, last pushed 7mo ago), licensed MIT. It adds 30 tokens to every session and 656 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-31.
Other skills, from other repositories
diffctx
Use when reviewing or explaining a commit, PR, branch or uncommitted diff — "review my last commit", "review before merge", "review my changes", "what else does this change affect" — the callers and tests the change reaches outside its diff, then the surrounding code.
simplicio-orient
Terminal-first execution — answer facts with the shell, never with the LLM. Use whenever a step needs a fact about the filesystem, git, processes, or system resources, or runs a build/test/lint/diff whose output would flood context. Substitutes deterministic shell/CLI calls for native LLM operations and clamps their…
simplicio-review
Deep, adversarial branch review — parallel subagents on separate rubrics (security/correctness, code-quality, and does-it-reproduce), spawned in one message, then deduped into one verdict. Runs for EVERY item, no TRIVIAL/SMALL shortcut — it is 3 of the 6 roles in simplicio-tasks' minimum-agent floor. Use before…
github-code-review
Review code changes by analyzing git diffs, leaving inline comments on PRs, and performing thorough pre-push review. Works with gh CLI or falls back to git + GitHub REST API via curl.
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.