Agent skill

Error Handling

by mobazha in mobazha/mobazha-unified

Guide for error handling patterns in Mobazha including ErrorBoundary hierarchy, API error handling, logging strategy, and graceful degradation.

MPL-2.0Auto-check passedDevelopment

Install Error Handling

skills CLI
$ npx skills add mobazha/mobazha-unified --skill error-handling -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mobazha/mobazha-unified error-handling --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mobazha/mobazha-unified.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/error-handling .claude/skills/error-handling && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
error-handling
GitHub stars
165
Token cost
~1.4k tokens
SKILL.md length
89 words
Files
1
Skills in repo
29
Repo updated
First seen
Licence
MPL-2.0

At a glance

Guide for error handling patterns in Mobazha including ErrorBoundary hierarchy, API error handling, logging strategy, and graceful degradation.

  • Adding error handling
  • SKILL.md covers 已有基础设施, 一、ErrorBoundary 层级, 二、API 错误处理 and 三、日志系统, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Working with ErrorBoundary

What it does

Error Handling is an agent skill from mobazha/mobazha-unified. Guide for error handling patterns in Mobazha including ErrorBoundary hierarchy, API error handling, logging strategy, and graceful degradation. Use when adding error handling, working with ErrorBoundary, or implementing fallback UI, "错误处理", "ErrorBoundary", "异常处理", "日志", "错误追踪", "降级".

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Error handling. The repository describes itself as: Open-source commerce frontend for storefronts, marketplaces, checkout, and seller management. The licence is MPL-2.0.

When your agent uses it

  • Adding error handling
  • Working with ErrorBoundary
  • Implementing fallback UI

Example prompts

  • “ErrorBoundary”
  • “/error-handling”

What it can do on your machine

Read from SKILL.md and the folder at commit 156c699. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Error Handling loads about 1.4k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 89 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~75
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mobazha/mobazha-unified at commit 156c699, republished under its MPL-2.0 licence (© mobazha). 89 words, ~1,412 tokens.

Download SKILL.mdSave it as .claude/skills/error-handling/SKILL.md (or your agent's skills folder).
name
error-handling
description
Guide for error handling patterns in Mobazha including ErrorBoundary hierarchy, API error handling, logging strategy, and graceful degradation. Use when adding error handling, working with ErrorBoundary, or implementing fallback UI, "错误处理", "ErrorBoundary", "异常处理", "日志", "错误追踪", "降级".

错误处理指南

Mobazha 项目的错误处理策略和已有基础设施。

已有基础设施

packages/core/services/monitoring/
├── errorTracker.ts        # ErrorTrackerService — 错误上报
├── logger.ts              # LoggerService — 日志系统
├── performanceMonitor.ts  # 性能监控
└── index.ts

apps/web/src/components/ErrorBoundary/
├── ErrorBoundary.tsx       # 通用错误边界
├── PageErrorBoundary.tsx   # 页面级错误边界
└── index.ts

一、ErrorBoundary 层级

层级策略
App Layout
  └── PageErrorBoundary(页面级)    ← 捕获整个页面的错误
        └── ErrorBoundary(组件级)  ← 捕获特定组件的错误
              └── 业务组件
页面级 ErrorBoundary
tsx
import { PageErrorBoundary } from '@/components/ErrorBoundary';

// 每个页面自动包裹(layout.tsx 中)
function OrdersPage() {
  return (
    <PageErrorBoundary pageName="订单列表">
      <OrderList />
    </PageErrorBoundary>
  );
}

特性:

  • 显示页面名称
  • 提供"重试"、"刷新"、"返回首页"操作
  • 开发模式显示错误详情
组件级 ErrorBoundary
tsx
import { ErrorBoundary } from '@/components/ErrorBoundary';

// 隔离风险组件,避免影响整个页面
function OrderDetail() {
  return (
    <div>
      <OrderInfo />
      <ErrorBoundary fallback={<p>图表加载失败</p>}>
        <PriceChart /> {/* 第三方图表可能崩溃 */}
      </ErrorBoundary>
    </div>
  );
}
适合添加 ErrorBoundary 的场景
场景推荐级别
第三方库组件(图表、编辑器)组件级
复杂数据转换和渲染组件级
每个路由页面页面级
钱包/交易相关 UI组件级

二、API 错误处理

标准模式
typescript
// 在 hook 中统一处理
function useOrderDetail(orderId: string) {
  const [data, setData] = useState(null);
  const [error, setError] = useState<string | null>(null);
  const [isLoading, setIsLoading] = useState(true);

  useEffect(() => {
    async function fetch() {
      try {
        setIsLoading(true);
        setError(null);
        const order = await ordersApi.getOrder(orderId);
        setData(order);
      } catch (err) {
        const message = err instanceof Error ? err.message : '加载失败';
        setError(message);

        // 上报到 ErrorTracker
        errorTracker.captureException(err instanceof Error ? err : new Error(message), {
          tags: { feature: 'orders', orderId },
        });
      } finally {
        setIsLoading(false);
      }
    }
    fetch();
  }, [orderId]);

  return { data, error, isLoading };
}
用户友好的错误提示
typescript
// 使用 i18n 翻译错误消息
const { t } = useI18n();

// 根据错误类型显示不同提示
function getErrorMessage(error: unknown): string {
  if (error instanceof TypeError && error.message.includes('fetch')) {
    return t('common.error.network'); // "网络连接失败"
  }
  if (error instanceof Error && error.message.includes('401')) {
    return t('common.error.unauthorized'); // "请重新登录"
  }
  return t('common.error.unknown'); // "出了点问题,请稍后重试"
}

三、日志系统

LoggerService 使用
typescript
import { logger } from '@mobazha/core';

// 基本使用
logger.info('订单创建成功', { orderId: '123' });
logger.warn('余额接近零', { balance: 0.001 });
logger.error('支付失败', error, { orderId: '123' });

// 子 Logger(带来源标签)
const chatLogger = logger.child('MatrixChat', { component: 'chat' });
chatLogger.info('消息发送成功', { roomId: 'room-123' });
// 输出: [MatrixChat] 消息发送成功 { roomId: 'room-123' }
日志级别选择
级别使用场景示例
debug开发调试函数入参、中间状态
info关键操作成功订单创建、钱包连接
warn可恢复的异常余额不足、网络超时重试
error不可恢复的错误API 500、合约调用失败
禁止日志中包含的内容
typescript
// ❌ 绝对禁止
logger.info('Token', { token: accessToken });
logger.debug('Mnemonic', { mnemonic: seedPhrase });
console.log('Private key:', privateKey);

// ✅ 安全的日志
logger.info('用户认证成功', { userId: user.id });
logger.error('交易失败', { txHash: tx.hash, errorCode: err.code });

四、ErrorTracker 使用

typescript
import { errorTracker } from '@mobazha/core';

// 捕获异常
errorTracker.captureException(error, {
  tags: { feature: 'payment', chain: 'ethereum' },
  extra: { orderId: '123', amount: '0.1 ETH' },
});

// 捕获消息(非异常的异常情况)
errorTracker.captureMessage('用户余额为负数', {
  level: 'warning',
  tags: { feature: 'wallet' },
});

// 面包屑(帮助重现问题路径)
errorTracker.addBreadcrumb({
  category: 'navigation',
  message: '进入订单详情',
  data: { orderId: '123' },
});
自动忽略的错误

ErrorTracker 已配置忽略以下常见噪音:

  • ResizeObserver loop limit exceeded
  • Loading chunk .* failed(代码分割加载失败)
  • Network request failed(网络断线)

五、网络断线处理

去中心化应用的特殊需求

Mobazha 作为去中心化应用,网络可靠性尤为重要:

typescript
// 1. 检测在线状态
if (!navigator.onLine) {
  // 显示离线提示(项目有 /offline 页面)
}

// 2. API 调用重试
import { retry } from '@mobazha/core';

const data = await retry(
  () => api.fetchData(),
  3, // 3 次重试
  1000, // 1s 初始延迟
  2 // 指数退避
);

// 3. WebSocket 重连(Matrix 已内置)
// useMatrixInit 自动处理断线重连

// 4. 交易状态恢复
// 交易发送后保存 txHash,页面刷新后可查询状态

六、优雅降级模式

typescript
// 功能不可用时的降级策略
function WalletBalance() {
  const { balances, error } = useWalletStore();

  if (error) {
    return (
      <div className="text-muted-foreground">
        <p>余额暂时无法加载</p>
        <button onClick={() => fetchBalances()}>重试</button>
      </div>
    );
  }

  return <BalanceDisplay balances={balances} />;
}

快速检查清单

  • 页面是否有 PageErrorBoundary 包裹?
  • 第三方组件是否有组件级 ErrorBoundary?
  • API 调用是否有 try/catch 和用户友好的错误提示?
  • 关键错误是否上报到 ErrorTracker?
  • 日志是否使用正确的级别?
  • 日志中是否不包含敏感信息?
  • 网络相关操作是否有重试机制?

© mobazha, MPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .cursor/skills/error-handling of mobazha/mobazha-unified.

Open the folder on GitHubat commit 156c699

Compare with similar skills

Error Handling next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Error Handling compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Error Handling this skillmobazha/mobazha-unified165—~1.4kAutomated safety check: PassMPL-2.0
Mole Bug Patternstw93/Mole70k—~2kAutomated safety check: PassGPL-3.0
Native Data FetchingCherryHQ/cherry-studio-app4k6 repos~2.9kAutomated safety check: NotesMIT
Rust Best Practicesfarm-fe/farm5.6k3 repos~1.1kAutomated safety check: PassMIT
R Function Input Validationtidyverse/dplyr5.1k1 repos~2.3kAutomated safety check: PassCustom licence
Next Best Practicesvercel-labs/openreview1.7k18 repos~1kAutomated safety check: PassNone

Similar skills

  • A catalog of recurring bug shapes in the Mole Mac cleaner, used to review safety-sensitive diffs for deletion safety, unbounded commands, shell traps and weak tests.

    70k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed
  • Native Data Fetching

    CherryHQ/cherry-studio-app

    A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.

    4k GitHub starsUsed in 6 repos~2.9k tokens
    DevelopmentAuto-check: notes
  • Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.

    5.6k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Validates arguments of exported R functions with the standalone check_* type checkers from rlang, in tidyverse style with clear error messages.

    5.1k GitHub starsUsed in 1 repo~2.3k tokens
    DevelopmentAuto-check passed
  • Next Best Practices

    vercel-labs/openreview

    Official

    Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

    1.7k GitHub starsUsed in 18 repos~1k tokens
    DevelopmentAuto-check passed
  • Error Handling

    microsoft/data-formulator

    Official

    统一错误处理系统。在添加 API 端点、修改错误处理、添加前端 API 调用、编写错误相关测试时使用. An agent skill from microsoft/data-formulator.

    18k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

More from mobazha/mobazha-unified

All 29 skills in this repo
  • A11y Guide

    mobazha/mobazha-unified

    Accessibility guide for Mobazha following WCAG 2.1 AA standards including color contrast, reduced motion, ARIA patterns, keyboard navigation, focus management, and screen reader testing.

    165 GitHub stars~1.4k tokensUpdated 5 days ago
    Auto-check passed
  • API Reference

    mobazha/mobazha-unified

    Look up Mobazha backend API endpoints, request/response formats, and field mappings.

    165 GitHub stars~1.7k tokensUpdated 5 days ago
    Auto-check passed
  • Code Review

    mobazha/mobazha-unified

    Review code for quality, architecture consistency, and adherence to Mobazha project standards using confidence-based filtering.

    165 GitHub stars~464 tokensUpdated 5 days ago
    Auto-check passed
  • Code Simplifier

    mobazha/mobazha-unified

    Simplify and refine recently written code for clarity, consistency, and maintainability while preserving all functionality.

    165 GitHub stars~601 tokensUpdated 5 days ago
    Auto-check passed
  • Commit Helper

    mobazha/mobazha-unified

    Generate commit messages and run pre-commit validation following Mobazha conventions.

    165 GitHub stars~735 tokensUpdated 5 days ago
    Auto-check passed
  • Component Dev

    mobazha/mobazha-unified

    Create and modify UI components following Mobazha conventions including directory structure, spacing standards, accessibility, and testing.

    165 GitHub stars~638 tokensUpdated 5 days ago
    Auto-check passed

Categories

Questions about Error Handling

What does Error Handling do?

Guide for error handling patterns in Mobazha including ErrorBoundary hierarchy, API error handling, logging strategy, and graceful degradation. Error Handling is an agent skill from mobazha/mobazha-unified. Guide for error handling patterns in Mobazha including ErrorBoundary hierarchy, API error handling, logging strategy, and graceful degradation.

When should I use Error Handling?

Error Handling fits situations like: adding error handling; working with ErrorBoundary; implementing fallback UI.

How do I install Error Handling in Claude Code?

Run `npx skills add mobazha/mobazha-unified --skill error-handling -a claude-code`. Or copy the skill folder (.cursor/skills/error-handling in mobazha/mobazha-unified) into .claude/skills/error-handling in your project. Claude Code loads it when a task matches its description.

How do I install Error Handling in Codex?

Run `npx skills add mobazha/mobazha-unified --skill error-handling -a codex`. Or copy the skill folder (.cursor/skills/error-handling in mobazha/mobazha-unified) into .agents/skills/error-handling in your project. Codex loads it when a task matches its description.

Can I use Error Handling in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mobazha/mobazha-unified --skill error-handling -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/error-handling, .gemini/skills/error-handling, .github/skills/error-handling and .opencode/skills/error-handling in your project.

What does Error Handling need to run?

SKILL.md names no scripts, command-line tools or credentials: Error Handling is instructions for the agent only.

Does Error Handling access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Error Handling safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Error Handling use?

Error Handling is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Error Handling use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Error Handling?

Skills that share tags, products or a category with Error Handling: Mole Bug Patterns (tw93/Mole, 70k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Rust Best Practices (farm-fe/farm, 5.6k stars) and R Function Input Validation (tidyverse/dplyr, 5.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Error Handling?

mobazha (a GitHub organization) maintains it in mobazha/mobazha-unified, which has 165 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 3, 2026.

Source: mobazha/mobazha-unified on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.