szymonkaliski/git-review
dotfiles/agents/skills/git-review/SKILL.md
Review uncommitted changes for issues, missed items, and improvements. Use when reviewing before commit or when user asks to check their work.
$ install --global
skillsauthnpx skillsauth add szymonkaliski/home-configuration git-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 2:24 AM4.5s1 file scanned
SKILL.md
- name:
- git-review
- description:
- Review uncommitted changes for issues, missed items, and improvements. Use when reviewing before commit or when user asks to check their work.
- argument-hint:
- [range]
- allowed-tools:
- Bash(git *), Read, Glob, Grep
- context:
- fork
- disable-model-invocation:
- true
Review the git diff and identify:
- Missed items: Incomplete implementations, forgotten edge cases, TODOs
- Issues: Bugs, security concerns, inconsistencies with existing patterns
- Improvements: Clarity, performance, maintainability
- Cleanup: Debug code, commented-out code, unnecessary changes
Changes
!git diff $ARGUMENTS
!git diff --cached
Provide a concise, actionable summary. If everything looks good, say so briefly.
Instructions
Before flagging an issue, read the relevant surrounding code to verify it's actually a problem. Specifically:
- If a change removes dedup/caching logic, check whether the receiver already handles duplicates before calling it out.
- If a change uses a variable or prop not shown in the diff, read the file to understand its type, source, and nullability before speculating.
- If a change modifies a condition or filter, check the call sites and data flow to confirm whether the new behavior is correct.
- If something looks like it could break, check for guards, fallbacks, or reconciliation logic elsewhere before reporting.
Do not flag something as an issue if the existing codebase already handles it. Only report confirmed or highly likely problems.
Related Skills
szymonkaliski/tdd
development
VerifiedTrustedCommunity
Test-driven bug fixing and feature development. Use when fixing bugs or building features — works with test suites or ad-hoc repro scripts. Enforces red-green-refactor vertical slices.
8SKILL.mdUpdated Apr 15, 2026
szymonkaliski/plan-review
tools
VerifiedTrustedCommunity
Open the current plan file in nvim for user review
8SKILL.mdUpdated Apr 15, 2026
szymonkaliski/git-commit
tools
VerifiedTrustedCommunity
Format, lint, test, and commit changes. Detects repo tooling automatically.
8SKILL.mdUpdated Apr 15, 2026
szymonkaliski/git-catchup
tools
VerifiedTrustedCommunity
Understand current work context from recent changes. Use at session start or when resuming work.
8SKILL.mdUpdated Apr 15, 2026