skills.rest
SimyV
SimyVCOMMUNITY
Explore all skills by this author →
GitHub

security

N/A

Updated Aug 27, 2026
Search Tags:#security#vulnerability#owasp#static-analysis#ci-cd#code-review#gate
One-click install
npx skills add https://github.com/SimyV/agent-system --skill security-simyv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/SimyV/agent-system/tree/main/config/skills/security
Command: npx skills add https://github.com/SimyV/agent-system --skill security-simyv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Static code review is time-consuming and error-prone; this skill automates security checks guided by OWASP Top 10 to accelerate safe releases.

Core Features & Use Cases

  • Static analysis of source code against OWASP Top 10 2025 best practices to identify injections, misconfigurations, insecure crypto, and data handling flaws.
  • Structured findings with severity, location, and remediation guidance for PR reviews and CI gate processes.
  • Use Case: integrate into pull requests to surface high-risk issues before merging and track remediation over time.

Quick Start

Run the skill against your repository to generate an OWASP-aligned findings report.

Frequently Asked Questions about security

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

FAQPage Schema
How do I automate secure code reviews for OWASP vulnerabilities in pull requests?▼

Automate secure code reviews by running static analysis on your source code to detect OWASP Top 10 2025 vulnerabilities, surfacing structured findings with severity, location, and remediation guidance directly in your pull requests.

Can I use static analysis to block insecure code from merging in my CI pipeline?▼

Yes, you can use static analysis as a security gate check in your CI pipeline to identify injections, misconfigurations, and insecure crypto, ensuring high-risk issues are flagged and triaged before merging code.

What types of security flaws does static analysis aligned with OWASP Top 10 detect?▼

Static analysis aligned with OWASP Top 10 detects injections, misconfigurations, insecure cryptography, and data handling flaws in source code, generating structured findings for triage and remediation tracking.

How do I structure security findings from code baselining for effective triage?▼

Structure security findings from code baselining by including severity levels, exact vulnerability locations, and recommended fixes, ensuring your team can efficiently triage and track remediation over time during PR reviews.

Does this static analysis approach work without external dependencies or components?▼

Yes, this static analysis approach works without external dependencies or components, allowing you to run it directly against your repository to generate an OWASP-aligned findings report immediately.

Why does static analysis for code review take so much time and how can I accelerate it?▼

Manual static code review is time-consuming and error-prone, but you can accelerate safe releases by automating security checks guided by OWASP Top 10 best practices to quickly surface high-risk issues.

Related Skills

Explore More Software Engineering Skills→
roderikroderik
2

codeql

Identify security vulnerabilities in source code using CodeQL static analysis.

Community
Advanced
drvossdrvoss
42

pr-security-review

Analyze pull request diffs for security vulnerabilities and remediation guidance.

Community
Advanced
alo-expalo-exp
6

GSD — Security Review

Review code changes against OWASP defense-in-depth and generate SECURITY.md gates.

Official
Advanced
icartshicartsh
4

code-analyze

Analyze .NET solutions for code quality, security, and dependency issues.

Community
Advanced