Skip to content
Skills Library
Security · Review & audit

secure-code-review

/secure-code-review

Perform a security-focused code review of a change or codebase — authentication, authorization (object/function level), input handling and injection, output encoding, cryptography, secrets, deserialization, SSRF, file handling, logging — with language-specific sinks and a findings format developers can act on. Use when reviewing a pull request for security, auditing a service before release, or verifying a reported vulnerability in source.

Repository
Claude-Blue ↗
Licence
MIT
Last repository change
01.11.2026

Assessment and security

100/ 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.
Content35 / 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
4
Deprecation

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

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Perform a security-focused code review of a change or codebase — authentication, authorization (object/function level), input handling and injection, output encoding, cryptography, secrets, deserialization, SSRF, file handling, logging — with language-specific sinks and a findings format developers can act on. Use when reviewing a pull request for security, auditing a service before release, or verifying a reported vulnerability in source.

Original author description

Perform a security-focused code review of a change or codebase — authentication, authorization (object/function level), input handling and injection, output encoding, cryptography, secrets, deserialization, SSRF, file handling, logging — with language-specific sinks and a findings format developers can act on. Use when reviewing a pull request for security, auditing a service before release, or verifying a reported vulnerability in source.

How it works

  1. Approach
  2. Sink cheat sheet
  3. Findings format
  4. Related skills
  5. References
Original SKILL.md headings · 49 lines, 370 words
SKILL.md preview
---
name: secure-code-review
description: Perform a security-focused code review of a change or codebase — authentication, authorization (object/function level), input handling and injection, output encoding, cryptography, secrets, deserialization, SSRF, file handling, logging — with language-specific sinks and a findings format developers can act on. Use when reviewing a pull request for security, auditing a service before release, or verifying a reported vulnerability in source.
license: MIT
metadata:
  category: appsec
  version: "2.0.0"
  verification: documented
---

# Secure Code Review

## Approach

1. Understand the feature and trust boundaries (what input is attacker-controlled? who is the caller?).
2. Trace **sources → sinks**: request params/headers/body, files, queue messages, webhooks, DB content written by users → dangerous operations.
3. Check **authorization on every handler** that touches an object by ID (BOLA/IDOR), not only authentication.
4. Review security-sensitive diffs line by line; for large codebases combine with SAST (`sast-triage`) and grep for sinks.

## Sink cheat sheet

| Class | Sinks / patterns to inspect |
|---|---|
| SQL/NoSQL injection | String-built queries: `cursor.execute(f"...{x}")`, `"SELECT ..." + x`, `$where`, `db.collection.find(JSON.parse(input))`, ORM `raw()`/`extra()` |
| Command injection | `subprocess` with `shell=True`, `os.system`, `Runtime.exec` with concatenated string, `child_process.exec`, backticks |
| Code injection / deserialization | `eval`, `exec`, `pickle.loads`, `yaml.load` (unsafe loader), Java `ObjectInputStream`, .NET `BinaryFormatter`, PHP `unserialize`, template rendering of user input (SSTI: `render_template_string`) |
| XSS | `innerHTML`, `dangerouslySetInnerHTML`, `v-html`, `|safe`, `Html.Raw`, unescaped template output, URL `javascript:` in href |
| SSRF | Server fetches user-supplied URL (`requests.get(url)`, `HttpClient`, image/PDF renderers, webhooks); check allow-list, DNS rebinding, redirects, cloud metadata (169.254.169.254) |
| Path traversal | `open(base + user_path)`, `send_file`, zip extraction without path checks (Zip Slip) |
| AuthN | Custom JWT parsing (`alg=none`, missing `exp`/`aud` checks), password hashing not bcrypt/scrypt/Argon2, session fixation, MFA bypass paths |
| AuthZ | Missing ownership check (`Order.get(id)` without `user_id`), role checks only in UI, mass assignment (binding all request fields to model) |
| Crypto | ECB mode, static IV/nonce, `Math.random()`/`random` for tokens, MD5/SHA1 for passwords, disabled TLS verification (`verify=False`, `InsecureSkipVerify`) |
| Secrets | Hard-coded keys, tokens in logs, secrets in client bundles |
| Logging | Missing audit of security events; logging PII/secrets; log injection (CRLF) |

## Findings format

```
[Severity] <Title> — <file>:<line>
Issue: <what and why exploitable>, attacker-controlled input: <source>
Impact: <data/privilege affected>
Fix: <specific code-level fix, e.g. use parameterized query / check order.owner_id == current_user.id>
Reference: <CWE-xxx, OWASP ASVS x.y.z>
```

Rate with exploitability + impact; avoid flagging theoretical issues without a reachable source.

## Related skills

`sast-triage`, `threat-modeling`, `security-requirements`, `api-authorization-testing`, `security-tool-development`

## References

- OWASP Code Review Guide: https://owasp.org/www-project-code-review-guide/
- OWASP ASVS 5.0: https://owasp.org/www-project-application-security-verification-standard/
- OWASP Cheat Sheet Series: https://cheatsheetseries.owasp.org/
- CWE Top 25: https://cwe.mitre.org/top25/

Versions

RepositoryScoreLicence
This page · kaandgnsh/Claude-Blue100MIT
helx0071/skillsmo100MIT
mohamed-osama-aboelkheir/appsec-untangled-resources100MIT
arozumenko/sdlc-skills100MIT
SkillMedev/skills100MIT
RobinBeraud/claude-qa-skills90MIT
Gattic/GatPi-Harness90MIT

Database snapshot: 13.11.2026 · package version ec97f399adf8 (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

  • 100security-audit
    Audits code for security issues and writes secure code, checking against the OWASP Top 10 risk categories with concrete, language-specific checks - broken access control and IDOR, injection, XSS, SSRF, authentication, sessions and JWTs, secrets, cryptography, unsafe…
  • 100security-review
    OWASP-style security review of code and configuration: secrets, injection, XSS, access control, authentication, sensitive data, SSRF, unsafe deserialization, dependencies and infrastructure. Use when a change touches user input, auth, API endpoints, file uploads, payments,…
  • 100security-and-hardening
    Use when writing or reviewing code that handles user input, authentication, access control, cryptography, error handling, file uploads, or dependency management. Also activates when a pull request touches any security-sensitive component.
  • 100securitycards
    Apply version-specific secure coding guidance to AI-generated or human-written code that uses supported open source libraries. Use when starting a software project, implementing a security-sensitive feature, or reviewing code for secure defaults, authentication, authorization,…
  • 100security-review
    Security-focused review of an open-source pull request or diff. Use when the change touches authentication or authorization, cryptography, token or session handling, input parsing, deserialization, subprocess or shell invocation, file path construction, uploads and archive…
  • 100secure-by-design-coding
    Proactive secure-coding companion that embeds security controls while code is being written. Use when implementing authentication, authorization, input handling, API endpoints, sessions, crypto, password hashing, file uploads, secrets, CORS/CSRF, rate limiting, or when asked to…

Feedback and reports

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