001-commands-inventory
Use when you need to generate a checklist document with embedded commands inventory,…
Use when you need to apply Java exception handling best practices — including using specific exception types, managing resources with try-with-resources, securing exception messages, preserving error context via exception chaining, validating inputs early with fail-fast
$ npx -y skills add jabrena/plinth --skill 126-java-exception-handling --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/126-java-exception-handlingContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when you need to apply Java exception handling best practices — including using specific exception types, managing resources with try-with-resources, securing exception messages, preserving error context via exception chaining, validating inputs early with fail-fast
name: 126-java-exception-handling description: Use when you need to apply Java exception handling best practices — including using specific exception types, managing resources with try-with-resources, securing exception messages, preserving error context via exception chaining, validating inputs early with fail-fast principles, handling thread interruption correctly, documenting exceptions with @throws, enforcing logging policy, translating exceptions at API boundaries, managing retries and idempotency, enforcing timeouts, attaching suppressed exceptions, and propagating failures in async/reactive code. This should trigger for requests such as Exception handling; Use try-with-resources in Java code; Create exception chaining in Java code; Apply fail-fast validation in Java code; Review Java exception taxonomy and propagation. Part of Plinth Toolkit license: Apache-2.0 metadata: author: Juan Antonio Breña Moral version: 0.19.0
Identify and apply robust Java exception handling practices to improve error clarity, security, debuggability, and system reliability.
**What is covered in this Skill?**
**Scope:** The reference is organized by examples (good/bad code patterns) for each core area. Apply recommendations based on applicable examples.
Before applying any exception handling changes, ensure the project compiles. If compilation fails, stop immediately — do not proceed until resolved. After applying improvements, run full verification.
1. **Compile project before exception-handling changes**
Run `./mvnw compile` or `mvn compile` and stop immediately if compilation fails.
2. **Read exception-handling reference**
Read `references/126-java-exception-handling.md` and identify applicable failure-handling and observability improvements.
3. **Apply exception-handling improvements**
Refactor to specific exceptions, safe resource handling, error translation, and consistent logging patterns.
4. **Verify with full build**
Run `./mvnw clean verify` or `mvn clean verify` after applying improvements.
For detailed guidance, examples, and constraints, see [references/126-java-exception-handling.md](references/126-java-exception-handling.md).
Languages: Español · 中文 Help this project grow: Become a sponsor
Use when you need to generate a checklist document with embedded commands inventory,…
Use when you need to generate a checklist document with embedded agents inventory, following…
Use when you need to generate a checklist document with Java system prompts from skills.xml,…
Use when you need to install the embedded project commands into command directories…
Use when you need to install the embedded robot agents into .github/agents, .claude/agents,…
Guides the creation of agile epics with comprehensive definition including business value,…