cluvo-find-handlers

Cluvo Find Handlers

Scan the project for error handling locations and wire up Cluvo at the right level.

Prerequisites

Check that @cluvo/sdk is installed (look for it in package.json dependencies). If not installed, tell the user:

@cluvo/sdk is not installed. Run /cluvo-setup first to install and set up basic integration.

Then stop.

Steps

1. Locate existing Cluvo reporter instance

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.

2. Scan for error handling locations

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 Cluvo
• Especially in command handlers, API routes, or service entry points

Category B: Process-level error handlers:

• process.on('uncaughtException', ...)
• process.on('unhandledRejection', ...)
• Check if these exist. If not, note their absence.

Category C: Throw/reject sites:

• Functions that throw custom errors or call Promise.reject
• These indicate where errors originate (useful context, not direct integration points)

3. Recommend integration level for each location

Present 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:

• try/catch in command handlers or top-level operations → reportAndPrompt (simplest) or manual reportError + promptAndSubmit
• try/catch wrapping an entire async function → wrap(fn) or wrap(fn, { rethrow: false })
• No global error handlers exist → Recommend installGlobalHandlers() at app startup
• reportError used without promptAndSubmit → Add installExitHandler() to catch unreported errors at exit
• try/catch where the caller needs fine-grained control (e.g., retry logic, custom formatting, conditional reporting) → Low-level pipeline

4. Apply with user confirmation

For 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.

5. Completion message

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

API Reference

Read references/sdk-api.md for the full Reporter API including reportAndPrompt, wrap, reportError, promptAndSubmit, installGlobalHandlers, installExitHandler, and low-level methods.