Skip to content
Skills Library
Security · Review & audit

code-review-security

/code-review-security

Security-focused code review mapped to OWASP Top 10 and ASVS. Use when reviewing pull requests, auditing files or modules for vulnerabilities, or performing pre-merge security gate checks. Covers injection, auth, authorization, cryptography, data exposure, misconfiguration, and deserialization.

Author
owasp ↗
Licence
CC-BY-4.0
Last repository change
15.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 15.10.2026, without references to retired models or APIs.

Licence

CC-BY-4.0, otwarta.

What it does and when to use it

Security-focused code review mapped to OWASP Top 10 and ASVS. Use when reviewing pull requests, auditing files or modules for vulnerabilities, or performing pre-merge security gate checks. Covers injection, auth, authorization, cryptography, data exposure, misconfiguration, and deserialization.

Original author description

Security-focused code review mapped to OWASP Top 10 and ASVS. Use when reviewing pull requests, auditing files or modules for vulnerabilities, or performing pre-merge security gate checks. Covers injection, auth, authorization, cryptography, data exposure, misconfiguration, and deserialization.

How it works

  1. Steps
  2. Output
  3. OWASP References
Original SKILL.md headings · 35 lines, 237 words
SKILL.md preview
---
name: code-review-security
description: Security-focused code review mapped to OWASP Top 10 and ASVS. Use when reviewing pull requests, auditing files or modules for vulnerabilities, or performing pre-merge security gate checks. Covers injection, auth, authorization, cryptography, data exposure, misconfiguration, and deserialization.
license: CC-BY-4.0
---

# Security Code Review

Review code for security vulnerabilities by following the full procedure in `plays/code-review-security.md`.

## Steps

1. **Scope & Context** — Establish language/framework, trust boundary (server/client/library/CLI), data sensitivity (PII, credentials, financial), and exposure (internet-facing, internal, local).

2. **Systematic Review by Vulnerability Class** (priority order):
   - **Injection (A03)** — SQL, command, XSS, SSTI, LDAP, path traversal, header, log injection
   - **Authentication & Session (A07)** — Hardcoded credentials, missing auth, weak sessions, JWT issues
   - **Authorization (A01)** — Missing authz checks, IDOR, horizontal/vertical privilege escalation
   - **Cryptography (A02)** — Weak algorithms, hardcoded keys, missing encryption, custom crypto
   - **Data Exposure (A01)** — Sensitive data in errors/logs, credentials in code, debug mode
   - **Misconfiguration (A05)** — Default credentials, permissive CORS, missing security headers
   - **Deserialization (A08)** — Untrusted deserialization, missing integrity checks, CSRF gaps

3. **Framework-Specific Checks** — Apply checks for detected framework (React, Express, Django, Flask, Spring, Rails, Go).

4. **Diff-Specific Analysis** (for PRs) — Focus on changed lines plus context, verify security controls preserved, check new endpoints match auth patterns, look for removed security controls.

5. **Produce Findings** — Cite file:line, show vulnerable snippet, explain attack scenario, provide fixed code, rate confidence.

## Output

Scope summary, findings sorted by severity using `templates/finding.md`, positive observations (good security controls in place), and severity count table.

## OWASP References

- OWASP Top 10 (2021): A01-A10
- OWASP ASVS v5.0
- OWASP Code Review Guide
- OWASP Cheat Sheet Series

Versions

RepositoryScoreLicence
This page · owasp/secure-agent-playbook90CC-BY-4.0
MaxMiksa/Auto-Company100MIT

Database snapshot: 13.11.2026 · package version ab43b9c4dff1 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95owasp-security
    Use when reviewing code for security vulnerabilities, implementing authentication/authorization, handling user input, or discussing web application security. Covers OWASP Top 10:2025, ASVS 5.0, and Agentic AI security (2026).
  • 100security-audit
    Use when reviewing code for security vulnerabilities, hardening an application, or deriving security requirements from OWASP/ASVS guidance.
  • 100owasp-security
    Reviews code for security vulnerabilities and guides secure implementation using OWASP Top 10:2025, ASVS 5.0, the OWASP Top 10 for LLM Applications (2026), and the OWASP Top 10 for Agentic Applications (2026). Use when reviewing code or a diff for security issues, implementing…
  • 100owasp-asvs
    OWASP ASVS v5.0 security verification skill with Drupal 11 mappings. Use when performing security code reviews, implementing security requirements, or verifying security compliance in Drupal projects.
  • 90owasp-security
    Review code being written or modified against the OWASP Top 10:2025 and ASVS secure-coding requirements, in any language or stack, catching vulnerability classes before they ship. Use when writing auth logic, handling user input, adding API endpoints, choosing cryptography,…
  • 100go-security-audit
    Security review for Go applications: input validation, SQL and command injection, SSRF, path traversal, auth, secrets, cryptography, TLS, CSRF and cookies, OWASP Top 10. Use when performing security reviews, checking for vulnerabilities, hardening Go services, or reviewing auth…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.