security

Run a comprehensive security review of code and configurations.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/hafidzlvm/opencode --skill security-hafidzlvm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/hafidzlvm/opencode/tree/main/.dsh/skills/security
Command: npx skills add https://github.com/hafidzlvm/opencode --skill security-hafidzlvm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security issues often slip into codebases unnoticed until they become incidents. This Skill performs a comprehensive security review so vulnerabilities, misconfigurations, and risky patterns are identified before deployment. ## Core Features & Use Cases - Comprehensive Security Review: Invokes a dedicated security review workflow that examines code for vulnerabilities and unsafe practices. - Argument-Driven Scope: Accepts user-provided arguments to focus the review on specific files, directories, or concerns. - Use Case: Before merging a pull request, run the security review on the changed files to catch issues like hardcoded secrets, injection risks, or insecure dependencies. ## Quick Start Ask the assistant to run a security review on the current project or a specific file, optionally describing the areas of concern.

Frequently Asked Questions about security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a security review on my code?▼

Invoke the security skill and optionally pass arguments describing the scope, such as specific files or directories. The skill loads the security review instructions and applies them to your codebase.

What does a comprehensive security review check for?▼

A security review examines code for common vulnerabilities such as injection flaws, hardcoded credentials, insecure configurations, and unsafe dependency usage. The exact checks are defined in the underlying security command instructions.

Can I scope the security review to specific files?▼

Yes. Any text you provide when invoking the skill is treated as arguments, so you can name files, directories, or particular concerns to focus the review on.

When should I run a security review during development?▼

Run it before merging pull requests, before releases, and after adding new dependencies or authentication logic. Regular reviews catch vulnerabilities earlier when they are cheaper to fix.

What are the limitations of an automated security review?▼

Automated reviews can miss business-logic flaws and context-dependent vulnerabilities. They complement but do not replace manual penetration testing and dedicated security audits for high-risk systems.