메뉴
Provides exception handling and logging standards including NPE prevention, try-catch-finally best practices, SLF4J usage, and log management. Invoke when user asks about exception handling or logging best practices.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Complete PRD template with AI-friendly markers. Use for product requirement docs: includes overview, requirements, processes, data, interfaces, acceptance. AI can quickly identify [AI] marked sections for implementation.
Provides API documentation template and standards for RESTful API, gRPC, and other interfaces. Includes request/response format, parameter definitions, error codes, and Markdown documentation structure. Invoke when generating API documentation or interface specifications.
Provides database design templates and documentation structure. Invoke when designing database schemas, creating database design documents, or generating SQL scripts.
Provides common Java coding standards including hutool tool usage and Lombok annotations. Invoke when generating Java code (DO, VO, Service, Controller) or applying coding standards.
Provides Java Controller layer standards including RESTful API design, request mapping, parameter validation, and response handling. Invoke when generating Controller files or RESTful API endpoints.
Provides Java DAO layer standards including interface specifications, MyBatis XML templates, method naming, parameter annotations, and CRUD operation patterns. Invoke when generating DAO files or MyBatis mappers.
| name | p3c-exception-logging |
| description | Provides exception handling and logging standards including NPE prevention, try-catch-finally best practices, SLF4J usage, and log management. Invoke when user asks about exception handling or logging best practices. |
本技能提供阿里巴巴Java开发手册中的异常处理和日志相关规范。
【强制】不要通过catch方式处理可预检查的RuntimeException（如NullPointerException、IndexOutOfBoundsException）
if (obj != null) {...}try { obj.method() } catch (NullPointerException e) {…}【强制】异常不要用来做流程控制、条件控制
【强制】catch时区分稳定代码和非稳定代码，对非稳定代码尽可能区分异常类型
【强制】捕获异常是为了处理它，不要捕获却什么都不处理
【强制】try块在事务代码中，catch异常后需要回滚事务时必须手动回滚
【强制】finally块必须对资源对象、流对象进行关闭，有异常也要做try-catch
【强制】不要在finally块中使用return
【强制】捕获异常与抛异常必须完全匹配，或捕获异常是抛异常的父类
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
private static final Logger logger = LoggerFactory.getLogger(Abc.class);
【强制】trace/debug/info级别日志必须使用条件输出或占位符方式
if (logger.isDebugEnabled()) {
logger.debug("Processing trade with id: " + id);
}
logger.debug("Processing trade with id: {} ", id);
【强制】避免重复打印日志，在log4j.xml中设置additivity=false
【强制】异常信息应包括案发现场信息和异常堆栈信息
【推荐】生产环境禁止输出debug日志；有选择地输出info日志；谨慎使用warn级别
【推荐】使用warn日志级别记录用户输入参数错误，非必要不使用error级别
【强制】velocity调用POJO类属性时直接使用属性名，模板引擎会自动调用getXxx()
【强制】后台输送给页面的变量必须加$!{var}
System.currentTimeMillis(); 而不是 new Date().getTime();