Menú
在代码变更落地后更新受影响的文档，确保 docs/ 与代码一致。包含必更新清单、更新原则、文档传感器验证。
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
派遣 build-error-resolver 修复构建/类型/依赖/配置错误，不建 session
中文版 Java / Spring Boot 工程规约与代码 Review 标准。覆盖 Jakarta Validation 参数校验、空安全工具类、常量与枚举、Lombok/POJO、异常与日志、安全、MySQL/ORM、并发、单元测试、工程分层与 Review 清单。当用中文进行 Java/Spring Boot 代码生成、改造或 Review 时加载。
Generates Spring Boot 3.x configurations, creates REST controllers, implements Spring Security 6 authentication flows, sets up Spring Data JPA or MyBatis-Plus data access, and configures reactive WebFlux endpoints. Use when building Spring Boot 3.x applications, microservices, or reactive Java applications; invoke for Spring Data JPA, MyBatis-Plus, Spring Security 6, WebFlux, Spring Cloud integration, Java REST API design, or Microservices Java architecture.
Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.
Builds security-focused full-stack web applications by implementing integrated frontend and backend components with layered security at every level. Covers the complete stack from database to UI, enforcing auth, input validation, output encoding, and parameterized queries across all layers. Use when implementing features across frontend and backend, building REST APIs with corresponding UI, connecting frontend components to backend endpoints, creating end-to-end data flows from database to UI, or implementing CRUD operations with UI forms. Distinct from frontend-only, backend-only, or API-only skills in that it simultaneously addresses all three perspectives—Frontend, Backend, and Security—within a single implementation workflow. Invoke for full-stack feature work, web app development, authenticated API routes with views, microservices, real-time features, monorepo architecture, or technology selection decisions.
Optimizes database queries and improves performance across PostgreSQL and MySQL systems. Use when investigating slow queries, analyzing execution plans, or optimizing database performance. Invoke for index design, query rewrites, configuration tuning, partitioning strategies, lock contention resolution.
| name | documentation |
| description | 在代码变更落地后更新受影响的文档，确保 docs/ 与代码一致。包含必更新清单、更新原则、文档传感器验证。 |
代码变更后的文档同步。只更新受影响的文档，不做无关改进。
直接修改 docs/ 下的文档；在 session README.md（或回报主会话）留变更笔记。完成后运行 node scripts/hooks/dispatcher.cjs stop 验证。
| 文档 | 触发条件 |
|---|---|
| API 文档 | 接口变更（参数 / 返回值 / 错误码） |
| README | 安装、使用方式变更 |
docs/ARCHITECTURE.md | 架构 / 模块边界 / 组件图变更 |
模块 CLAUDE.md | 模块行为或入口变更 |
| 文档 | 触发条件 |
|---|---|
| 代码注释 | 复杂逻辑、关键算法、设计决策 |
| 配置文档 | 配置项变更（新增 / 默认值 / 移除） |
| 部署文档 | 部署流程或环境要求变更 |
| 信号 | 行动 |
|---|---|
| 测试未通过就更新文档 | 先完成测试 phase |
| 文档与代码描述冲突 | 以代码为准修正文档 |
| dispatcher stop 报错 | 先修 [FAIL] 再 ship |
| 想跳过文档更新 | 检查是否真的零受影响文档 |
