This skill should be used when the user asks to "制定 Java 代码风格规范", "审查 Java 代码风格", "按团队规范重构 Java 代码", "统一 Spring Boot 后端代码风格", "将个人编码心得沉淀为规范", or asks for Java style guides, review checklists, naming conventions, exception/logging standards, or code-style-based refactoring. Use proactively for Java/S
This skill should be used when the user asks to "制定 Java 代码风格规范", "审查 Java 代码风格", "按团队规范重构 Java 代码", "统一 Spring Boot 后端代码风格", "将个人编码心得沉淀为规范", or asks for Java style guides, review checklists, naming conventions, exception/logging standards, or code-style-based refactoring. Use proactively for Java/Spring backend style discussions even when the user only says "帮我看下这段代码是否规范".
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.