security-review

Identifies and remediates security risks in Django/DRF backend code.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/arsen-ask-lx/.claude_file_4all --skill security-review-arsen-ask-lx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/arsen-ask-lx/.claude_file_4all/tree/main/skills/security-review
Command: npx skills add https://github.com/arsen-ask-lx/.claude_file_4all --skill security-review-arsen-ask-lx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Security reviews often miss subtle misconfigurations and insecure defaults in backend code during code reviews and audits. This Skill provides a structured checklist to proactively identify hardcoded secrets, SQL injection, XSS, CSRF, PII exposure in logs, and permission-related issues across endpoints.

Core Features & Use Cases

  • Hardcoded secrets, token leakage, and secret management checks.
  • SQL injection, XSS, CSRF, and logging of PII checks across Django/REST code.
  • Permissions and endpoint hardening checks to ensure proper access control and production-ready defaults.
  • Use Case: During a security audit, apply this checklist to a repository's endpoints, authentication flows, and file uploads to surface critical vulnerabilities before release.

Quick Start

Integrate this checklist into your code review process to identify and remediate security issues in backend code.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I check for SQL injection and XSS vulnerabilities during a backend code review?

A security review checklist helps identify and remediate backend vulnerabilities like SQL injection, XSS, and CSRF by systematically auditing endpoints, permissions, and authentication flows during code reviews.

What is the best way to prevent hardcoded secrets and PII exposure in Django applications?

Preventing hardcoded secrets and PII exposure in Django applications requires a security audit checklist that verifies secret management practices and inspects logging configurations to ensure sensitive data is not leaked in production.

How do I review file upload handling and permissions in a Django REST Framework project?

Reviewing file upload handling and permissions in a Django REST Framework project involves checking endpoint hardening, validating access controls, and applying a security checklist to ensure proper authorization and production-ready defaults.

Does this security review checklist cover CSRF protection and rate limiting for API endpoints?

Yes, the security review checklist covers CSRF protection and rate limiting for API endpoints, alongside checks for token leakage, permissions, and production security defaults to ensure comprehensive backend hardening.

Can I use this security checklist for auditing existing backend repositories before release?

Yes, you can use this security checklist for auditing existing backend repositories before release by applying it to endpoints, authentication flows, and file uploads to surface critical vulnerabilities and insecure configurations.