nickolashkraus/review-file
.claude/skills/review-file/SKILL.md
Review a file for typos, bugs, inaccuracies, and inconsistencies.
testing
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add nickolashkraus/dotfiles review-fileInstall 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 16, 2026, 2:36 PM43.6s1 file scanned
SKILL.md
- name:
- review-file
- description:
- Review a file for typos, bugs, inaccuracies, and inconsistencies.
- disable-model-invocation:
- false
- allowed-tools:
- Bash, Edit, Glob, Grep, Read
- argument-hint:
- <file>
You are reviewing a file. The file path is $ARGUMENTS.
Step 1: Read the file
Read the file in full. You need complete context to review.
Step 2: Review the file
Go through the entire file. Check for:
- Typos: Misspelled words, wrong variable names, copy/paste errors.
- Bugs: Logic errors, off-by-one mistakes, null/undefined risks, missing error handling, race conditions, resource leaks.
- Inaccuracies: Incorrect comments, misleading names, stale references, wrong values or constants.
- Inconsistencies: Naming conventions that break from the rest of the file, mismatched types, formatting that diverges from surrounding code, style violations.
Read surrounding files when needed to understand intent or verify correctness.
Step 3: Report findings
Present findings grouped by category. For each issue:
- State the line number and the problematic text.
- Explain what is wrong.
- Suggest the fix.
If you find issues, fix them directly. If the fix is ambiguous, prompt the user for input. Lean more toward just fixing the issue.
If the file is clean, say so.
Related Skills
nickolashkraus/fact-check
tools
VerifiedTrustedCommunity
Check the veracity of a claim against notes, documentation, and resources. Takes a string argument or reads from the clipboard.
SKILL.mdUpdated Apr 17, 2026
nickolashkraus/write-trd
development
VerifiedTrustedCommunity
Generates a Technical Requirements Document through structured interviews and codebase analysis.
SKILL.mdUpdated Apr 16, 2026
nickolashkraus/update-notion-page
content-media
VerifiedTrustedCommunity
Update a Notion page with the Markdown contents of a local file.
SKILL.mdUpdated Apr 16, 2026
nickolashkraus/update-linear-issue
content-media
VerifiedTrustedCommunity
Update a Linear issue with the Markdown contents of a local file.
SKILL.mdUpdated Apr 16, 2026