Borrowing it
Nothing to install: this file belongs to briancl2/CustomerNewsletter. 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/briancl2/CustomerNewsletter/main/.github/skills/reviewing-code-locally/SKILL.mdgit clone --depth 1 https://github.com/briancl2/CustomerNewsletterWrote 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/briancl2/customernewsletter/reviewing-code-locally)<a href="https://agentmods.dev/skills/briancl2/customernewsletter/reviewing-code-locally"><img src="https://agentmods.dev/badge/skills/briancl2/customernewsletter/reviewing-code-locally/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/briancl2/customernewsletter/reviewing-code-locally"><img src="https://agentmods.dev/badge/skills/briancl2/customernewsletter/reviewing-code-locally.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.00080 | $0.00837 |
| Opus 5 | $0.00040 | $0.00418 |
| Sonnet 5 | $0.00016 | $0.00167 |
| Haiku 4.5 | $0.00008 | $0.00084 |
Grade A, and why
reviewing-code-locally 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 9d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Code Locally
Fast local code review of staged git changes via Copilot CLI. Reviews staged diffs with full file context, applying repo-specific rules from AGENTS.md automatically.
Quick Start
git add <files>
make review
How It Works
flowchart LR
STAGE["git add"] --> SCRIPT["scripts/local_review.sh"]
SCRIPT --> DIFF["git diff --cached"]
SCRIPT --> CTX["Full file contents"]
SCRIPT --> PROMPT["Review prompt template"]
DIFF --> COMBINE["Assemble prompt"]
CTX --> COMBINE
PROMPT --> COMBINE
COMBINE --> CLI["copilot -p"]
CLI --> STDOUT["Findings → terminal"]
Workflow / Steps
Step 1: Stage changes
Stage the files you want reviewed:
git add <files>
Step 2: Run review
make review
The script:
- Captures
git diff --cached - Reads full contents of each changed file (up to 500 lines per file)
- Substitutes diff + file context into the review prompt template
- Runs
copilot -p "<prompt>" --no-color -s - Prints findings to stdout
Step 3: Act on findings
Review the severity-tagged findings and fix as needed. Re-stage and re-run.
Review Prompt
The review prompt is stored at references/review-prompt.md within this skill directory. It is generic — it works in any repo. Repo-specific rules (deletion discipline, governed paths, artifact cleanliness, etc.) are picked up automatically from AGENTS.md, which Copilot CLI loads by default.
The prompt covers:
- Correctness — bugs, security, dead code, error handling
- Cross-File Consistency — undefined terms, broken references, heading hierarchy
- Language-Specific Quality — shell, Python, YAML, Markdown
- Style — only when it meaningfully hurts readability
Output Format
Findings use severity levels: CRITICAL, HIGH, MEDIUM, LOW, NIT.
Each finding includes file path, line range, description, and suggested fix. Ends with a one-line summary count.
Known Limitations
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 98 lines · 80 tokens per session scan A 4325635ca9b0
reviewing-code-locally is a skill published in the GitHub repository briancl2/CustomerNewsletter (11 stars, last pushed 3mo ago), licensed MIT. It adds 80 tokens to every session and 837 once invoked, about $0.0004 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-30.
Other skills, from other repositories
github-review-pr
Review GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents. Use this skill whenever the user wants to review a PR, asks for code review on a pull request, mentions "review PR", "check this PR", "look at pull request", or references a PR number or GitHub PR URL. Do NOT use for…
github-review-pr
Review GitHub pull requests with evidence-backed, multi-perspective analysis and false-positive filtering. Use when the user asks to review, inspect, or check a GitHub pull request by number or URL. Default to reporting findings locally; publish comments, submit reviews, or approve only when the user explicitly…
hunk-extensions
Maps the hunkdiff/extension authoring surface for Hunk, the terminal diff viewer — hiding or reordering reviewed files, docked panes, alternate file views, commands and key bindings, dialogs, workspace writes, themes, syntax languages, VCS backends, lifecycle events. Use when writing, debugging, or installing a Hunk…
hunk-launch-video
Produces Hunk videos by driving the real TUI headlessly in a PTY, compositing captioned 1080p frames in Chromium, and encoding with ffmpeg. Use for feature demos, workflow explainers, announcements, launch videos, and full-release roundups.
hunk-release
Prepares, publishes, verifies, and curates Hunk releases. Use for release metadata, benchmarks, tags, publishing, release videos, backports, or recovery.
hunk-review
Interacts with live Hunk diff review sessions via CLI. Inspects review focus, navigates files, hunks, and exact lines, reloads session contents, adds inline review comments, and paints attention marks on character ranges. Use when the user has a Hunk session running or wants to review diffs interactively.