\r \r

JAR 包冲突检测 Skill — Spring Boot 微服务\r

\r

目的\r

\r To detect version conflicts, known incompatible dependency pairs, and duplicate JARs\r in Spring Boot microservice projects (Maven or Gradle), and produce an actionable\r conflict report with resolution suggestions.\r \r

触发场景\r

\r Use this skill when the user:\r

• Reports runtime errors such as NoSuchMethodError, ClassNotFoundException, LinkageError\r
• Asks to check or analyze JAR conflicts, version convergence, or dependency tree issues\r
• Is upgrading Spring Boot (e.g., 2.x → 3.x) and needs conflict validation\r
• Wants a dependency health check before CI/CD deployment\r
• Mentions Spring Cloud + Spring Boot version mismatch\r \r

工作流程\r

\r

Step 1 — 确认项目目录和构建工具\r

\r Ask the user for (or infer from context):\r

1. Project root directory — path to the Maven/Gradle project (containing pom.xml or build.gradle)\r
2. Build tool — auto-detected if not specified (maven | gradle | auto)\r
3. Report format — html (default, visual) | txt | json (for CI)\r
4. Severity level — all (default) | warn | error\r \r For multi-module projects, always point to the parent/root directory so all sub-modules are scanned.\r \r

Step 2 — 运行检测脚本\r

\r Run the bundled detection script:\r \r

python scripts/detect_conflicts.py \\r
  --project-dir \x3C用户项目路径> \\r
  --output conflict-report.html \\r
  --mode auto \\r
  --level all\r
```\r
\r
**Script capabilities:**\r
- Runs `mvn dependency:tree` (Maven) or `gradle dependencies` (Gradle) to get the full resolved dependency tree\r
- Falls back to static `pom.xml` parsing if Maven/Gradle CLI is unavailable\r
- Detects **version conflicts**: same `groupId:artifactId`, different versions across modules\r
- Detects **known incompatible pairs**: e.g., Spring Boot 3.x + Spring 5.x, dual SLF4J bindings\r
- Generates reports in HTML / TXT / JSON format\r
\r
**Output files:**\r
- `conflict-report.html` — visual HTML report (default, recommended)\r
- `conflict-report.txt` — plain text for terminal review\r
- `conflict-report.json` — machine-readable for CI integration\r
\r
### Step 3 — 解读结果并给出建议\r
\r
After scanning, present results clearly:\r
\r
1. **总结** — X 个 ERROR，Y 个 WARN，依赖总数\r
2. **逐条解读** — 对每个 ERROR 级冲突说明原因和影响\r
3. **给出修复方案** — 参考 `references/conflict_patterns.md` 提供具体 POM/Gradle 修改示例\r
\r
For resolution guidance, load `references/conflict_patterns.md` which contains:\r
- Common conflict patterns and fixes\r
- Spring Boot / Spring Cloud / Hibernate version compatibility matrix\r
- SLF4J binding conflict resolution\r
- javax → jakarta migration guide\r
- Maven Enforcer plugin setup for CI enforcement\r
\r
### Step 4 — 可选：生成修复建议 POM 片段\r
\r
If the user wants specific fixes, generate the corresponding `dependencyManagement`\r
XML snippet or Gradle `resolutionStrategy` block inline in the reply.\r
\r
## 输出格式指南\r
\r
- **HTML 报告** — 默认推荐，适合人工审查，call `preview_url` or `open_result_view`\r
- **JSON 报告** — 适合 CI pipeline 解析，结合 `jq` 过滤 ERROR 级别\r
- **TXT 报告** — 适合终端快速查看\r
\r
## 注意事项\r
\r
- If `mvn`/`gradle` is not available on PATH, the script falls back to static POM parsing\r
  (less accurate — transitive dependencies won't be resolved). Inform the user.\r
- For **Spring Boot 3.x migration**, always check for `javax.*` → `jakarta.*` conflicts.\r
- For **multi-module projects**, run from the **root directory** with the parent `pom.xml`.\r
- Script exit code: `0` = no ERROR conflicts; `1` = at least one ERROR found (useful for CI gates).\r
- All Python stdlib only — no pip install required.\r