From cluvo-plugin
Analyze a project's codebase to find error handling locations (try/catch, process error handlers, throw/reject sites) and apply the appropriate Cluvo API level (manual reportError, installGlobalHandlers, or low-level pipeline) at each location. TRIGGER when: user asks to "find error handlers for cluvo", "cluvo 수동 연동", "apply reportError", "에러 핸들링 위치 찾아줘", "cluvo-find-handlers".
How this skill is triggered — by the user, by Claude, or both
Slash command
/cluvo-plugin:cluvo-find-handlersThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Scan the project for error handling locations and wire up Cluvo at the right level.
Scan the project for error handling locations and wire up Cluvo at the right level.
Check that @cluvo/sdk is installed (look for it in package.json dependencies). If not installed, tell the user:
@cluvo/sdkis not installed. Run/cluvo-setupfirst to install and set up basic integration.
Then stop.
Search for new Reporter( in the codebase to find the existing reporter instance and its variable name (e.g., cluvo, reporter). If not found, tell the user to run /cluvo-setup first.
Search the project source files for these patterns:
Category A: Existing try/catch blocks:
try { ... } catch blocks that handle errors but don't report them to CluvoCategory B: Process-level error handlers:
process.on('uncaughtException', ...)process.on('unhandledRejection', ...)Category C: Throw/reject sites:
throw custom errors or call Promise.rejectPresent findings to the user as a table:
| Location | Category | Recommendation |
|---|---|---|
src/commands/deploy.ts:45 | try/catch | reportAndPrompt (or reportError + promptAndSubmit) |
| (global) | No global handler | installGlobalHandlers() |
src/services/api.ts:20 | try/catch (wrappable) | wrap with rethrow: false |
src/api/client.ts:89 | try/catch (pipeline) | Low-level API |
| (process exit) | No exit handler | installExitHandler() |
Decision rules:
reportAndPrompt (simplest) or manual reportError + promptAndSubmitwrap(fn) or wrap(fn, { rethrow: false })installGlobalHandlers() at app startupinstallExitHandler() to catch unreported errors at exitFor each recommended location, show the code change and ask the user to confirm before applying.
Read references/error-handling-patterns.md for integration patterns: reportAndPrompt, wrap, manual level (reportError + promptAndSubmit), global handlers (installGlobalHandlers), exit handler (installExitHandler), nested reporters, and low-level pipeline.
Error handler integration complete. Cluvo will now capture errors at the configured locations.
Next step:
- To customize sanitize rules, labels, or issue format → use
/cluvo-custom-config
Read references/sdk-api.md for the full Reporter API including reportAndPrompt, wrap, reportError, promptAndSubmit, installGlobalHandlers, installExitHandler, and low-level methods.
npx claudepluginhub maintainer-ally/cluvo --plugin cluvo-pluginCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.