better-result

Enforce opt-in governance rules for adopting the better-result library.

6|1|Updated Jun 1, 2025
One-click install
npx skills add https://github.com/rezics/rezics --skill better-result-rezics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: better-result
Source: https://github.com/rezics/rezics/tree/main/.agents/skills/better-result
Command: npx skills add https://github.com/rezics/rezics --skill better-result-rezics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes clear governance over when to introduce better-result, preventing default adoption and guiding explicit opt-in decisions.

Core Features & Use Cases

  • Provides guardrails for when to adopt or avoid better-result in a codebase.
  • Documents adoption and migration workflows, including child skills for adoption and v2 migration.
  • Guides teams to maintain consistency in error handling without forcing changes across modules.

Quick Start

Review the root SKILL.md and the child skills to determine if better-result should be adopted or migrated in your module.

Frequently Asked Questions about better-result

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
When should I introduce the better-result library for TypeScript error handling?

Introduce the better-result library for TypeScript error handling only when touching error-handling patterns during feature work, bug fixes, or refactors, ensuring explicit opt-in rather than default adoption. It provides guardrails to guide when adoption or migration is appropriate for a module.

How do I migrate to better-result v2 for tagged errors in TypeScript?

To migrate to better-result v2 for tagged errors, review the root SKILL.md and its child skills which document the v2 migration workflow. These child skills guide the migration process to maintain consistency in error handling without forcing changes across unrelated modules.

What are the guardrails for adopting tagged errors in TypeScript modules?

Guardrails for adopting tagged errors require explicit opt-in decisions governed by the better-result rules. This prevents default adoption across a codebase and maintains consistency in error handling by guiding teams on when to specifically adopt or avoid the library within targeted modules.

Can I use better-result for TypeScript error-handling refactors without migrating the entire codebase?

Yes, you can use better-result for TypeScript error-handling refactors without migrating the entire codebase. It establishes governance to guide explicit opt-in decisions per module, maintaining error-handling consistency without forcing changes across modules that are not undergoing refactoring.

Why prevent default adoption of better-result in TypeScript projects?

Preventing default adoption of better-result in TypeScript projects avoids uncontrolled codebase changes. It establishes clear governance over when to introduce the tagged-errors library, ensuring teams make explicit opt-in decisions only when error-handling patterns are actively touched during development.

Does the better-result Skill require any specific dependencies to implement TypeScript error-handling guardrails?

The better-result Skill requires no external dependencies to implement TypeScript error-handling guardrails. It operates as a governance framework requiring only a SKILL.md frontmatter with name and description, along with optional child skills for adoption and migration workflows.