skills.rest
YanCheng-go
YanCheng-goCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

security-review

Identify security risks across codebases, dependencies, secrets, and Supabase RLS policies.

3|Updated Mar 1, 2026
Search Tags:#security#rls#owasp#dependencies#audit#secrets#devsecops
One-click install
npx skills add https://github.com/YanCheng-go/danskprep --skill security-review-yancheng-go
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/YanCheng-go/danskprep/tree/main/.claude/skills/security-review
Command: npx skills add https://github.com/YanCheng-go/danskprep --skill security-review-yancheng-go

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This security review helps teams perform a structured audit of codebases, dependencies, secrets, and Supabase RLS policies to reduce vulnerabilities and exposure.

Core Features & Use Cases

  • OWASP Top 10 coverage: identify and report common web application security risks.
  • Dependency and secret scanning: detect vulnerable packages and exposed credentials in code history and working tree.
  • RLS policy verification: validate that Row-Level Security is enabled and properly restricted across tables.
  • Use Case: run on a PR to validate security posture before merge and produce a concise remediation plan.

Quick Start

Run the security audit against the current codebase or a pull request to identify OWASP risks and misconfigurations.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I audit my codebase for OWASP Top 10 vulnerabilities?▼

Run a security review against your codebase or specific PR to identify OWASP Top 10 vulnerabilities, checking tooling configurations, client usage patterns, and environment variable exposure to produce a remediation plan.

How do I check for exposed secrets and vulnerable dependencies in a pull request?▼

Validate tooling and configurations by checking npm audit results for vulnerable packages and scanning the code history and working tree for secret leakage before merging a pull request.

Does this security review verify Supabase Row-Level Security policies?▼

Yes, this security review verifies Supabase Row-Level Security policies by validating that RLS is enabled and properly restricted across tables, checking client usage patterns to ensure correct coverage.

Can I run a DevSecOps audit on my current codebase without external dependencies?▼

Yes, you can run a DevSecOps audit on your current codebase without external dependencies to detect vulnerable packages, exposed credentials, and misconfigurations, producing a structured remediation plan.

What is the best way to validate environment variable exposure before a merge?▼

The best way to validate environment variable exposure is to run a comprehensive security audit that checks tooling configurations and client usage patterns to identify and report security risks pre-merge.

Related Skills

Explore More Software Engineering Skills→
the-inconvenience-storethe-inconvenience-store
1

getting-up-to-speed

Summarize project state, git status, working tree changes, and open beads.

Community
Advanced
Blake-JohnBlake-John

security-reviewer

Identify security vulnerabilities and generate structured audit reports with severity ratings.

Community
Advanced
CenredJunCenredJun

security-auditor

Scan JavaScript, TypeScript, and Python codebases for vulnerabilities and secrets.

Community
Advanced
marvinbissmarvinbiss

supabase-audit-tables-read

Read Supabase tables to verify data exposure and RLS effectiveness.

Community
Intermediate