Awesome-omni-skill security-review
Scan code changes for security vulnerabilities including OWASP Top 10, hardcoded secrets, injection flaws, and authentication issues. Use after implementation to catch security problems before marking a task complete.
install
source · Clone the upstream repo
git clone https://github.com/diegosouzapw/awesome-omni-skill
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/testing-security/security-review-patleeman" ~/.claude/skills/diegosouzapw-awesome-omni-skill-security-review-ea21a8 && rm -rf "$T"
manifest:
skills/testing-security/security-review-patleeman/SKILL.mdsource content
Security Review
Perform a security review of all code changes you just made for this task.
What to check
- Hardcoded secrets: API keys, passwords, tokens, connection strings in source code
- Injection: SQL injection, command injection, XSS via unsanitized user input
- Input validation: Is all external input validated at system boundaries?
- Authentication & authorization: Are sensitive endpoints protected? Are permissions checked?
- Data exposure: Are error messages leaking internal details? Are logs safe?
- Dependencies: Any known-vulnerable packages or insecure configurations?
- Cryptography: Weak algorithms, hardcoded IVs, missing encryption for sensitive data?
- Race conditions: TOCTOU bugs, shared mutable state without synchronization?
Instructions
- Review each file you changed or created with a security mindset
- If you find vulnerabilities, fix them immediately
- For secrets found in code, replace with environment variables
- For injection flaws, add parameterized queries or input sanitization
- After fixing, verify the fix doesn't break functionality
- Summarize findings with severity (critical / high / medium / low)