devlearn-security

Scan code diffs for security risks and generate fix-and-teach blocks.

1|Updated May 24, 2026
One-click install
npx skills add https://github.com/mrdulasolutions/DevLearn --skill devlearn-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devlearn-security
Source: https://github.com/mrdulasolutions/DevLearn/tree/main/devlearn-security
Command: npx skills add https://github.com/mrdulasolutions/DevLearn --skill devlearn-security

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps you prevent real security failures while coding by teaching secure patterns for secrets, authentication, XSS/injection risks, dependency hygiene, HTTPS, and error leakage.

Core Features & Use Cases

  • Security triage for real diffs: Scans for high-signal issues like committed .env, client-bundled API keys, unsafe HTML rendering, injection-prone SQL, missing HTTPS, verbose production errors, missing auth on sensitive routes, and risky dependencies.
  • Fix-and-teach workflow: Guides a safe order of operations—stop any active secret leak first, apply a minimal fix, then generate a lesson block that fits a viber or seasoned persona.
  • Pre-release security pass + handoffs: Provides a concise checklist and routes to related lifecycle skills (pre-ship, devops, deploy, post-ship) and devlearn-apis for auth implementation details.

Quick Start

Ask your AI agent to run /devlearn-security to review the current diff for secrets, auth gaps, XSS/injection risks, dependency issues, HTTPS enforcement, and production error leakage, then produce the fix steps and a short teach-back lesson.

Frequently Asked Questions about devlearn-security

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

FAQPage Schema
How do I scan code diffs for secrets exposure and authentication weaknesses before shipping?

Run a security review on your current diff to identify committed secrets, missing auth on sensitive routes, and unsafe rendering. The scan produces triage output and fix steps to mitigate application security risks before release.

What is the best way to prevent XSS and SQL injection vulnerabilities in new features?

Prevent XSS and SQL injection by scanning user input rendering and database queries during security review. The process detects unsafe HTML rendering and injection-prone SQL, then generates minimal fixes and a teach-back lesson on secure coding patterns.

How do I check dependencies for supply-chain risks before a release?

Check dependencies for supply-chain risks by including them in your pre-release security pass. The review flags risky dependencies alongside other high-signal issues and routes results to a checklist with lifecycle handoffs for remediation.

Does this security review work for diffs that touch crypto or payment processing?

Yes, the security review is designed for diffs touching crypto, payments, auth, and user input rendering. It applies scenario-based triage to identify information leakage, insecure transport, and other application security risks specific to sensitive features.

How do I redact exposed API keys and enforce HTTPS in my application?

Redact exposed API keys and enforce HTTPS by following the fix-and-teach workflow. It prioritizes stopping active secret leaks first, applies minimal fixes for missing HTTPS, and generates persona-tailored lessons to prevent future exposure.