What problem does it solve? Manually reviewing large Java codebases for security issues is slow and error-prone, especially in monorepos with multiple frameworks and CMS products. This Skill runs deterministic static audits that surface vulnerable dependencies, hardcoded credentials, and insecure framework configurations with file/line evidence. ## Core Features & Use Cases - Project Probing: Detects build systems (Maven/Gradle), frameworks (Spring Boot, Shiro, Struts2, and 9 more), and CMS products (RuoYi, MCMS, Halo), then recommends the right audit tools. - Dependency SCA & Secrets Scanning: Extracts Maven/Gradle/JAR dependencies to flag risky components and scans for hardcoded passwords, API keys, JDBC credentials, JWTs, and private keys. - Framework & CMS Config Audits: Runs per-framework architecture baselines and configuration audits, plus dedicated rules for known CMS products, with monorepo module scoping and tunable detection modes. - Use Case: Given a RuoYi-Cloud monorepo, probe the project, scope the audit to specific modules, then produce a severity-sorted findings report covering vulnerable dependencies, leaked secrets, and Shiro misconfigurations. ## Quick Start Run a Java static security audit on the project at /path/to/project and summarize all findings by severity.