Skip to content
Skills Library
Security · Review & audit

secure-code-review

/secure-code-review

Review a diff or a module for security flaws, focused on business web applications: broken access control and IDOR, injection (SQL, command, LDAP, XPath), XSS in Angular templates and bypassSecurityTrust, CSRF, insecure deserialisation, SSRF, file upload and path traversal, authentication and session handling, secrets and sensitive data exposure, with evidence and a fix per finding. Use when reviewing a pull request that touches endpoints, authentication, files, queries or user input, or when asked for a security review.

Licence
MIT
Last repository change
10.11.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 10.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

Review a diff or a module for security flaws, focused on business web applications: broken access control and IDOR, injection (SQL, command, LDAP, XPath), XSS in Angular templates and bypassSecurityTrust, CSRF, insecure deserialisation, SSRF, file upload and path traversal, authentication and session handling, secrets and sensitive data exposure, with evidence and a fix per finding. Use when reviewing a pull request that touches endpoints, authentication, files, queries or user input, or when asked for a security review.

Original author description

Review a diff or a module for security flaws, focused on business web applications: broken access control and IDOR, injection (SQL, command, LDAP, XPath), XSS in Angular templates and bypassSecurityTrust, CSRF, insecure deserialisation, SSRF, file upload and path traversal, authentication and session handling, secrets and sensitive data exposure, with evidence and a fix per finding. Use when reviewing a pull request that touches endpoints, authentication, files, queries or user input, or when asked for a security review.

How it works

  1. Approach
  2. Checklist (.NET / Angular)
  3. Output
Original SKILL.md headings · 24 lines, 259 words
SKILL.md preview
---
name: secure-code-review
description: "Review a diff or a module for security flaws, focused on business web applications: broken access control and IDOR, injection (SQL, command, LDAP, XPath), XSS in Angular templates and bypassSecurityTrust, CSRF, insecure deserialisation, SSRF, file upload and path traversal, authentication and session handling, secrets and sensitive data exposure, with evidence and a fix per finding. Use when reviewing a pull request that touches endpoints, authentication, files, queries or user input, or when asked for a security review."
---

# Secure code review

## Approach
1. **Entry points** in the diff: controllers/endpoints, message handlers, file imports, scheduled jobs reading external data.
2. Follow **untrusted data** from each entry point to sinks (database, shell, file system, HTML, HTTP calls, deserialiser).
3. Check **authorisation** at each operation on a resource, server-side, including tenant scoping.

## Checklist (.NET / Angular)
| Risk | Look for | Fix |
|---|---|---|
| Broken access control / IDOR | `GET /invoices/{id}` without checking ownership or tenant | resource-based authorisation, tenant filter |
| SQL injection | string concatenation in SQL, `FromSqlRaw` with interpolated input | parameters, `FromSql` interpolation, stored procedures with parameters |
| XSS | `[innerHTML]`, `bypassSecurityTrustHtml`, Razor `@Html.Raw` | Angular sanitisation, encode output, CSP |
| CSRF | cookie auth + state-changing GET or no antiforgery token | antiforgery, SameSite cookies, no GET side effects |
| Deserialisation | `BinaryFormatter`, `TypeNameHandling.All` | System.Text.Json, no polymorphic type names from input |
| SSRF | server fetches a user-provided URL | allow-list hosts, block internal ranges |
| File upload / path traversal | user file name used in a path, no type/size check | generated names, `Path.GetFileName`, size limit, content check, storage outside web root |
| Sensitive data | personal data or secrets in logs, errors, URLs | ids only, generic error messages |
| Crypto | MD5/SHA1 for passwords, custom crypto, hard-coded keys | ASP.NET Identity hasher / PBKDF2+, Key Vault |

## Output
Findings: severity, location, exploit scenario in one sentence, fix, test to add. State what was **not** reviewed.

Versions

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

Database snapshot: 13.11.2026 · package version a855b83ed353 (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-review
    Reviews changed code for realistic security risks in authn/authz, input handling, injection, secrets, uploads, SSRF, CSRF/XSS, webhooks, dependencies, and local-agent shell or file access. Use when a change touches auth, user input, endpoints, payments, uploads, shell execution, or sensitive data.
  • 95vibe-security
    Comprehensive secure coding guide covering OWASP web vulnerabilities with prevention patterns and checklists. Use when writing or reviewing web application code to prevent XSS, CSRF, SSRF, SQL injection, access control flaws, and other common security vulnerabilities.
  • 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,…
  • 100code-review-security
    Security-focused code review checklist and automated scanning patterns. Use when reviewing pull requests for security issues, auditing authentication/authorization code, checking for OWASP Top 10 vulnerabilities, or validating input sanitization. Covers SQL injection prevention,…
  • 90security-reviewer
    Dedicated security-audit route for OWASP-style risks, secret leaks, auth flaws, injection, unsafe input handling, SSRF/XSS, and sensitive-data exposure. Use instead of code-reviewer when the prompt explicitly asks for security, vulnerability, threat, auth, or OWASP review.

Feedback and reports

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