Review codebases for auth, secrets, validation, and logging risks.
npx skills add https://github.com/hoonzinope/skills --skill security-reviewer-hoonzinope
Please help me install this Agent Skill. Skill: security-reviewer Source: https://github.com/hoonzinope/skills/tree/main/security-reviewer Command: npx skills add https://github.com/hoonzinope/skills --skill security-reviewer-hoonzinope
This Skill helps security teams identify and document security weaknesses in authentication, secret handling, input validation, and logging, without touching production code, enabling fast, auditable reviews.
Run a security review on the target application and generate the findings to .documents/_ops/SECURITY_AUDIT.md.
High-intent search queries and answers about installing and using this skill.
To audit authentication and secrets management vulnerabilities, you can run a security review that analyzes code for risks in auth, secret handling, and logging without modifying source code. It generates findings in a reproducible SECURITY_AUDIT.md file.
The best way to document security risks during a code review is to generate a dated audit trail in SECURITY_AUDIT.md. This ensures reproducible tracking of threats across authentication, validation, and logging without altering production code.
Yes, you can perform pre-release security validation across different application stacks. The review identifies threats and governance gaps in services and APIs regardless of the stack, writing results to a designated audit file.
No, the security audit process does not modify your source code. It writes findings to .documents/_ops/SECURITY_AUDIT.md, ensuring reproducible, dated audit trails while keeping the application and services untouched.
You need to generate a security audit report for compliance and governance during code reviews, threat modeling, or pre-release security validation. It documents input validation, logging, and authentication risks to identify governance gaps.
Input validation checking in automated security reviews works by analyzing the codebase for threats and logging weaknesses without touching source code. It documents these findings in a dated audit trail file for reproducible security tracking.
hoonzinopeAudit dependencies for updates, vulnerabilities, licenses, and unused packages.
goffityAudit JavaScript, TypeScript, Python, and Go code for OWASP Top 10 risks and hardcoded secrets.
florianbuetowScan code and dependencies for vulnerabilities mapped to CWEs.
iulianditaAudit application codebases, configurations, and CI/CD pipelines for security vulnerabilities.
