Convert TypeScript throws into tagged errors with cause chains.
npx skills add https://github.com/franky47/taskmaster --skill errore-franky47
Please help me install this Agent Skill. Skill: errore Source: https://github.com/franky47/taskmaster/tree/main/.agents/skills/errore Command: npx skills add https://github.com/franky47/taskmaster --skill errore-franky47
errore brings Go-style error handling to TypeScript by returning errors as values (Error | T) instead of throwing, enabling safer, more predictable control flow and easier debugging. This pattern reduces unhandled exceptions and supports typed error metadata, cause chaining, and type guards.
Use errore to implement error-as-values patterns across your TypeScript project.
High-intent search queries and answers about installing and using this skill.
To handle TypeScript errors as values, you adopt a Go-style pattern by returning typed errors alongside results, converting thrown exceptions into structured values using boundary conversion utilities like .catch and errore.try for synchronous code.
To type and pattern-match errors in TypeScript asynchronous APIs, define domain errors with createTaggedError and inspect cause chains using matchError and findCause, enabling structured pattern matching and robust composable flows.
To convert third-party library exceptions into structured typed errors in TypeScript, apply error conversion at code boundaries using .catch for asynchronous rejections, transforming unstructured throws into tagged errors with metadata and cause chains.
Yes, you can implement Go-style error handling in TypeScript without losing type safety by returning typed error values, using type guards to narrow error properties, and enforcing flat control flow with early returns for predictable execution.
Using error-as-values boundary patterns instead of try-catch blocks reduces unhandled exceptions by isolating external library errors at I/O boundaries, keeping core application logic flat, deterministic, and easier to debug with typed cause chains.
Yes, errore supports inspecting nested error cause chains in TypeScript by providing utilities like findCause to traverse the chain and partition to split results, enabling precise error identification and targeted recovery logic.
tchawla827Enforce strict typing and safe API design in TypeScript projects.
sgcarstrendsDiagnose production errors by tracking logs and system health.
hypeJunctionImplement robust error handling patterns for TypeScript applications.
darylmcdTrace a symbol or file:line across control, data, and exception paths in C#.
