code-quality

Name: code-quality
Availability: InStock
Author: Uygnoey

Standardize error handling and code review practices across a codebase.

Updated Mar 4, 2026

Search Tags:#typescript #architecture #code-quality #error-handling #code-review #result-pattern #adev-error

Ready to run

npx skills add https://github.com/uygnoey/autonomous-dev-agent-ts --skill code-quality-uygnoey

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-quality
Source: https://github.com/uygnoey/autonomous-dev-agent-ts/tree/main/.claude/skills/code-quality
Command: npx skills add https://github.com/uygnoey/autonomous-dev-agent-ts --skill code-quality-uygnoey

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams struggle with inconsistent code quality across projects; this Skill provides a centralized set of rules for error handling, result types, and review checks to standardize practices and reduce defects.

Core Features & Use Cases

Enforces Result<T, E> patterns for all public functions to improve error signaling.
Provides a taxonomy of AdevError types (ConfigError, AuthError, RagError, AgentError, PhaseError, ContractError, McpError) to categorize failures and support structured handling.
Supplies a reusable code-review checklist to improve PR quality and maintainability.

Quick Start

Integrate the Result pattern in new modules and apply the review checklist to ongoing code reviews.

Frequently Asked Questions about code-quality

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

FAQPage Schema

How do I standardize error handling in TypeScript projects?▼

Standardize TypeScript error handling by enforcing Result<T, E> patterns for public functions and applying a defined taxonomy of AdevError types to categorize failures and support structured handling across services.

What is the Result pattern for predictable error flows?▼

The Result pattern uses Result<T, E> types for public functions to improve error signaling, ensuring failures are handled predictably rather than relying on untyped exceptions across your codebase.

How do I enforce consistent code quality during code reviews?▼

Enforce consistent code quality during reviews by applying a reusable code-review checklist that validates Result<T, E> usage, checks error categorization, and guides PR quality and maintainability.

Does this code quality approach require any specific dependencies?▼

No dependencies are required. You can integrate the Result pattern and code-review checklist into existing TypeScript modules, services, and libraries without installing additional packages or external libraries.

What types of errors should I categorize when structuring TypeScript error handling?▼

Categorize failures using the AdevError taxonomy, which includes ConfigError, AuthError, RagError, AgentError, PhaseError, ContractError, and McpError to support structured error handling across modules.

When should I apply the Result pattern in my codebase?▼

Apply the Result pattern to all new modules and public functions to ensure robust type-safety and predictable error flows, then use the review checklist to maintain standards during ongoing QA.