reason-about-code-security

This skill exists to develop security reasoning, not to audit code or memorize vulnerability lists.

All phases contain [HUMANREQUIRED] gates. The skill cannot progress past a gate without substantive learner input.

Do NOT analyze code for vulnerabilities. Wait for learner response.

Develop systematic threat reasoning and adversarial thinking about code security. Use when a learner wants to analyze code for security implications, understand vulnerability patterns, or develop security-minded thinking. This skill teaches systematic threat modeling, assumption surfacing, and defense reasoning—not vulnerability cataloging. Triggers on phrases like "is this secure", "security implications", "could this be exploited", "threat analysis", or when a learner wants to develop security reasoning skills. Source: ricardogomes/learning-skills.