Agent Skills › AjayIrkal23/agentic-mercy-10x › backend-error-handling

backend-error-handling

GitHub

规范后端错误处理，定义错误分类、统一响应信封及HTTP状态码映射。确保日志安全脱敏，隐藏内部细节，实现服务层与控制器层的职责分离。

skills/backend-error-handling/SKILL.md AjayIrkal23/agentic-mercy-10x

Trigger Scenarios

定义后端错误类或分类体系设计集中式错误处理器审查日志记录与安全脱敏行为将领域错误映射为HTTP状态码

Install

npx skills add AjayIrkal23/agentic-mercy-10x --skill backend-error-handling -g -y

More Options

Use without installing

npx skills use AjayIrkal23/agentic-mercy-10x@backend-error-handling

指定 Agent (Claude Code)

npx skills add AjayIrkal23/agentic-mercy-10x --skill backend-error-handling -a claude-code -g -y

安装 repo 全部 skill

npx skills add AjayIrkal23/agentic-mercy-10x --all -g -y

预览 repo 内 skill

npx skills add AjayIrkal23/agentic-mercy-10x --list

SKILL.md

Frontmatter

{
    "name": "backend-error-handling",
    "schema": 1,
    "category": "backend",
    "surfaces": [
        "backend"
    ],
    "triggers": {
        "paths": [],
        "intents": [
            "backend"
        ],
        "keywords": [
            "backend",
            "behavior",
            "centralized",
            "client-safe",
            "defining",
            "error",
            "handler",
            "handling",
            "logging",
            "mapping",
            "redaction",
            "safe",
            "taxonomy"
        ]
    },
    "platforms": [
        "linux",
        "darwin",
        "windows"
    ],
    "token-cost": 482,
    "description": "ALWAYS invoke when defining backend error taxonomy, centralized handler behavior, safe logging, redaction, or client-safe error mapping.",
    "disable-model-invocation": false
}

Backend Error Handling

Overview

Backend failures must be structured, safe, and predictable.

This skill owns the error taxonomy, centralized handler behavior, and the rule that clients never see raw internal failures.

Use When

Defining or reviewing backend error classes.
Mapping domain errors to HTTP status codes.
Designing centralized error handling.
Reviewing safe logging and redaction behavior.

Do Not Use

Service/controller boundary questions by themselves.
API query semantics by themselves.
Performance tuning without error-handling impact.

Standard Error Envelope

{
  "success": false,
  "error": {
    "code": "ERROR_CODE",
    "message": "Safe user-facing message",
    "details": {}
  }
}

Rules:

success must be false
error.code is required
message must be safe for clients
details is optional and should stay narrow

Status Code Rules

400 validation
401 unauthorized
403 forbidden
404 not found
409 conflict
429 rate limited
500 internal error

Centralized Handler Rules

Normalize internal errors into the public error envelope.
Log safely.
Hide stack traces and internal implementation details from clients.
Keep controllers from building ad hoc error payloads unless they are only delegating to a shared formatter.