Repo lint report

What It Does

A pure-skill review of the current git diff. No MCP, no subagents, no hooks. Claude runs git commands directly and classifies each hunk into security, performance, or style categories, then prints a grouped report with file:line citations.

When It Triggers

• ▸"Lint this diff"
• ▸"Review my PR before I open it"
• ▸"Check this change for issues"

SKILL.md

---
name: repo-lint-report
description: Reviews the current git diff and reports style, security, and performance issues with file:line citations. Use when user says "lint this", "review my diff", or "check this PR for issues".
---

# Repo Lint Report

## When to Use
- User asks to lint, review, or audit a git diff
- After a multi-file change, before opening a PR

## Steps
1. Run `git diff --cached` to inspect staged changes
2. For each hunk, classify issues:
   - Security (injection, missing auth, secret leaks)
   - Performance (N+1 queries, missing indexes, sync I/O in async)
   - Style (naming, dead code, comments)
3. Produce a grouped report: file:line — severity — suggested fix
4. Finish with a one-line verdict (ship / fix-first / block)

Why This Shape

The three classification buckets (security, performance, style) match real review priorities. The final one-line verdict (ship / fix-first / block) gives the user a clear next action instead of a wall of text.

Gotchas

• ▸Works best on diffs under 500 lines — larger diffs should go through parallel-code-audit with subagents.
• ▸"Security" classifications need the project's threat model to avoid noise on low-risk code.
• ▸Claude's findings are suggestions, not gates — keep a human reviewer on high-stakes code paths.