security-guidance

You can get real-time security prompts by initiating this skill during your coding session to scan file changes for XSS, command injection, and hardcoded secrets, guiding you toward safe alternatives and best practices.

Proactive security guidance for code editing provides real-time vulnerability alerts and safe alternatives during development. You need it when writing web apps, APIs, or libraries to prevent common issues like CSRF and command injection before they enter production.

Yes, you can trigger this skill when reviewing a pull request to surface potential security concerns in modified files, specifically checking for hardcoded secrets, CSRF, and insecure authentication patterns.

Yes, this security guidance applies during code writing, reviews, and file edits across web apps, APIs, and library projects to enforce checks for command injection, unescaped inputs, and insecure data handling.

Common vulnerabilities detected during code editing sessions include command injection, XSS, CSRF, hardcoded secrets, unescaped inputs, and insecure authentication patterns, which are flagged to prevent issues before production.