181-java-observability-logging
This Claude Code skill provides guidance for implementing and improving Java logging and observability using SLF4J with Logback or Log4j2. Use it when adding logging support, refactoring existing logs, or enhancing observability across Java projects through proper log level selection, parameterized logging, sensitive data masking, environment-specific configuration, and log aggregation monitoring. The skill includes best practices for security-conscious logging, testing validation, and centralized log monitoring integration.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/181-java-observability-logging && cp -r /tmp/181-java-observability-logging/skills/181-java-observability-logging ~/.claude/skills/181-java-observability-loggingSKILL.md
# Java Logging Best Practices Implement effective Java logging following standardized frameworks, meaningful log levels, core practices (parameterized logging, exception handling, no sensitive data), flexible configuration, security-conscious logging, monitoring and alerting, and comprehensive logging validation through testing. **What is covered in this Skill?** - Standardized framework selection: SLF4J facade with Logback or Log4j2 - Meaningful and consistent log levels: ERROR, WARN, INFO, DEBUG, TRACE - Core practices: parameterized logging, proper exception handling, avoiding sensitive data - Configuration: environment-specific (logback.xml, log4j2.xml), output formats, log rotation - Security: mask sensitive data, control log access, secure transmission, GDPR/HIPAA compliance - Log monitoring and alerting: centralized aggregation (ELK, Splunk, Loki), automated alerts - Logging validation through testing: assert log messages, verify formats, test levels, measure performance impact **Scope:** The reference is organized by examples (good/bad code patterns) for each core area. Apply recommendations based on applicable examples. ## Constraints Before applying any logging recommendations, ensure the project compiles. Compilation failure is a blocking condition. After applying improvements, run full verification. - **MANDATORY**: Run `./mvnw compile` or `mvn compile` before applying any change - **SAFETY**: If compilation fails, stop immediately — do not proceed until resolved - **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` after applying improvements - **BEFORE APPLYING**: Read the reference for detailed good/bad examples, constraints, and safeguards for each logging pattern ## When to use this skill - Improve logging - Apply logging - Refactor logging - Add logging support ## Workflow 1. **Compile project before logging changes** Run `./mvnw compile` or `mvn compile` and stop immediately if compilation fails. 2. **Read logging reference and assess current observability** Read `references/181-java-observability-logging.md` and evaluate framework usage, log levels, sensitive-data handling, and config gaps. 3. **Apply logging and observability improvements** Implement selected framework/configuration/practice changes, including secure logging and monitoring integration where applicable. 4. **Verify with full build** Run `./mvnw clean verify` or `mvn clean verify` after applying improvements. ## Reference For detailed guidance, examples, and constraints, see [references/181-java-observability-logging.md](references/181-java-observability-logging.md).
Use when you need to generate a checklist document with Java system prompts, following the embedded template exactly and producing INVENTORY-SKILLS-JAVA.md in the project root. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @001-skills-inventory. Part of cursor-rules-java project
Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory. Part of cursor-rules-java project
Use when you need to install the embedded robot agents into either .cursor/agents or .claude/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Copy robot agents. Part of cursor-rules-java project
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of cursor-rules-java project
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic. Part of cursor-rules-java project
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of cursor-rules-java project
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. This should trigger for requests such as Create ADR for functional requirements; Document functional requirements; Capture functional requirements; Generate functional requirements in an ADR. Part of cursor-rules-java project