Does it support Bun-specific debugging?

Yes, it is designed for Bun-first shared infrastructure, including support for Bun package management and environment diagnostics.

How does it help with MCP (Model Context Protocol) issues?

It verifies tool registration sequences, ensures async handler compliance, and checks for missing field descriptions in Zod schemas required by AI models.

When should I use the escalation path?

Escalation is recommended when the investigation reveals a bug within the core @outfitter packages themselves rather than in your local implementation code.

What is the Outfitter Debugger skill?

It is a specialized capability for Claude to methodically diagnose issues within the @outfitter infrastructure, producing structured investigation reports and suggested fixes.

Can it fix TypeScript type errors?

Yes, it specifically identifies common pitfalls like missing awaits or variable reassignment that break Result-type narrowing, providing corrected code patterns.

Outfitter Debugger

Name: Outfitter Debugger
Author: outfitter-dev

byoutfitter-dev

•

Analytics & Monitoring

Provides a systematic, evidence-based debugging framework for diagnosing and fixing issues within Outfitter-based Bun projects.

The Debug Outfitter skill automates the diagnostic process for projects built using the @outfitter ecosystem, ensuring developers identify root causes rather than applying surface-level fixes. It guides Claude through a structured multi-stage workflow—from initial evidence collection and category-specific investigation (covering Result handling, MCP tools, CLI output, and logging) to producing high-confidence debug reports. This skill is essential for troubleshooting complex TypeScript type-narrowing issues, Bun runtime errors, and Model Context Protocol (MCP) registration failures while maintaining architectural consistency via the Outfitter Atlas.

Key Features

01Categorized Diagnostic Patterns for MCP, CLI, Results, and Logging

02Integrated Outfitter-Atlas expertise for architectural compliance

03Automated exit code and validation schema verification

042 GitHub stars

05Structured Root Cause Analysis (RCA) report generation

06Systematic Evidence Collection for logs, stack traces, and exit codes

Use Cases

01Troubleshooting failed MCP tool registrations or schema description mismatches

02Resolving TypeScript type-narrowing breaks in Result-based error handling workflows

03Investigating incorrect CLI exit codes or missing log output in Bun-first applications

Key Features

01Categorized Diagnostic Patterns for MCP, CLI, Results, and Logging

02Integrated Outfitter-Atlas expertise for architectural compliance

03Automated exit code and validation schema verification

042 GitHub stars

05Structured Root Cause Analysis (RCA) report generation

06Systematic Evidence Collection for logs, stack traces, and exit codes

Use Cases

01Troubleshooting failed MCP tool registrations or schema description mismatches

02Resolving TypeScript type-narrowing breaks in Result-based error handling workflows

03Investigating incorrect CLI exit codes or missing log output in Bun-first applications