← ClaudeAtlas

python-domain-exception-policylisted

Use when, and only when, the user explicitly requests Python exception classes or hierarchies, raise/catch boundaries, exception translation or chaining, traceback preservation, or an internal exception taxonomy or bounded retry classification for internal failures. Do not use this skill merely because another feature can fail or needs user-facing failure behavior.
genaptic/skillsets · ★ 1 · AI & Automation · score 70
Install: claude install-skill genaptic/skillsets
# Outcome Produce a concrete, reviewable result for the workflow below without overstating what was observed, executed, or verified. ## Compatibility Portable across Claude Code, Codex, and OpenCode. The optional auditor requires Python 3.11, performs static AST analysis without importing code, and uses no network. Confirm framework cancellation and exception-group semantics for the target runtime. ## Use this skill when - A library or application needs a deliberate public exception hierarchy. - Broad catches, silent failures, duplicate logging, or lost tracebacks need review. - Lower-level dependency errors need translation into domain contracts. - Cleanup, warnings, deprecations, cancellation, or retry behavior is unclear. - Internal exception taxonomy or translation boundaries must also map to CLI messages, streams, and exit statuses; also use `python-cli-error-output`. ## Do not use this skill when - The outcome is exclusively user-facing CLI messages, stdout/stderr, debug mode, and exit status without internal exception-taxonomy or translation work; use `python-cli-error-output`. - The outcome is an HTTP, RPC, or message-protocol error schema. - The task is merely to add one test without changing the error contract. ## Inputs Inspect or obtain: - Public callers and the actions they can take for each failure. - Current exception classes, catch blocks, logging calls, context managers, and retries. - Process, task, request, transaction, and external-dependency