troubleshooting
Skill0 starsChanged 10 months agoMITView on GitHub
Patrones maestros de manejo de errores en múltiples lenguajes incluyendo excepciones, tipos Result, propagación de errores y degradación elegante para construir aplicaciones resilientes. Usar cuando se implementa manejo de errores, se diseñan APIs o se mejora la confiabilidad de aplicaciones.
26 other projects use a version of this.
Adopted by
Most recently taken up by
- thistleknot/skillstheir own version, first seen Nov 8, 2026
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- onelastcommit/noctratheir own version, first seen Nov 8, 2026
- zakirkun/slayerclawtheir own version, first seen Nov 8, 2026
- snowfluke/tech-lead-skillstheir own version, first seen Nov 8, 2026
- jkitchin/knowhowtheir own version, first seen Nov 1, 2026
Used with
Projects with it also use task-breakdown and architecture.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ttmouseSkilltask-breakdown
专业的任务拆解器,将复杂需求拆分成"独立可运行与可演示"的最小闭环任务卡。严格按照纵向切片、单一数据变化、单一入口原则,确保每张任务卡都能在单回合实现并验证。当用户说"帮我拆解一下任务"、"用任务拆解器分析"、"按规范拆分"或需要将一个大的开发需求拆分成可执行的小任务时使用。输出格式严格按照[src/renderer/TODO.md]标准存储。
Also in 3 projects that use this
AnthropicSkillarchitecture
Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
Also in 3 projects that use this
Other versions26 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 26
- ChromeDevTools/chrome-devtools-mcp★ 55ksame name
- cartography-cncf/cartography★ 4.2ksame name
- jasonkneen/kiro★ 753same name
- nanvix/nanvix★ 318same name
- duyet/clickhouse-monitoring★ 303same name
- davidYichengWei/agentic-engineering-framework★ 158same name
- projectbluefin/finpilot★ 131same name
- mycelium-io/mycelium★ 127same name
- NVIDIA/elements★ 115same name
- emanueleielo/ciana-parrot★ 77same name
16 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- brainstormingSkill
- planningSkill
- creating-skillsSkill
- ceo-orchestratorSkill
- brand-identitySkill
- generador-imagenes-satoriSkill
- growth-divisionSkill
- product-divisionSkill
- operations-divisionSkill
The file
Files
Patrones de Manejo de Errores
Construye aplicaciones resilientes con estrategias robustas de manejo de errores que manejan fallos elegantemente y proporcionan excelentes experiencias de debugging.
Cuándo Usar Este Skill
- Implementando manejo de errores en nuevas funcionalidades
- Diseñando APIs resilientes a errores
- Debuggeando issues de producción
- Mejorando la confiabilidad de aplicaciones
- Creando mejores mensajes de error para usuarios y desarrolladores
- Implementando patrones de retry y circuit breaker
- Manejando errores async/concurrentes
- Construyendo sistemas distribuidos tolerantes a fallos
Conceptos Fundamentales
1. Filosofías de Manejo de Errores
Excepciones vs Tipos Result:
- Excepciones: Try-catch tradicional, interrumpe flujo de control
- Tipos Result: Éxito/fallo explícito, enfoque funcional
- Códigos de Error: Estilo C, requiere disciplina
- Tipos Option/Maybe: Para valores nullable
Cuándo Usar Cada Uno:
- Excepciones: Errores inesperados, condiciones excepcionales
- Tipos Result: Errores esperados, fallos de validación
- Panics/Crashes: Errores irrecuperables, bugs de programación
2. Categorías de Errores
Errores Recuperables:
- Timeouts de red
- Archivos faltantes
- Input de usuario inválido
- Límites de rate de API
Errores Irrecuperables:
- Sin memoria
- Stack overflow
- Bugs de programación (null pointer, etc.)
Patrones por Lenguaje
Python - Manejo de Errores
Jerarquía de Excepciones Personalizadas:
class ApplicationError(Exception):
"""Excepción base para todos los errores de aplicación."""
def __init__(self, message: str, code: str = None, details: dict = None):
super().__init__(message)
self.code = code
self.details = details or {}
self.timestamp = datetime.utcnow()
class ValidationError(ApplicationError):
"""Se lanza cuando falla la validación."""
pass
class NotFoundError(ApplicationError):
"""Se lanza cuando el recurso no se encuentra."""
passRetry con Backoff Exponencial:
def retry(max_attempts: int = 3, backoff_factor: float = 2.0, exceptions: tuple = (Exception,)):
"""Decorador retry con backoff exponencial."""
def decorator(func):
@wraps(func)
def wrapper(*args, **kwargs):
last_exception = None
for attempt in range(max_attempts):
try:
return func(*args, **kwargs)
except exceptions as e:
last_exception = e
if attempt < max_attempts - 1:
sleep_time = backoff_factor ** attempt
time.sleep(sleep_time)
continue
raise
raise last_exception
return wrapper
return decoratorTypeScript/JavaScript - Manejo de Errores
Clases de Error Personalizadas:
class ApplicationError extends Error {
constructor(
message: string,
public code: string,
public statusCode: number = 500,
public details?: Record<string, any>
) {
super(message);
this.name = this.constructor.name;
}
}
class ValidationError extends ApplicationError {
constructor(message: string, details?: Record<string, any>) {
super(message, 'VALIDATION_ERROR', 400, details);
}
}Patrón de Tipo Result:
type Result<T, E = Error> =
| { ok: true; value: T }
| { ok: false; error: E };
function Ok<T>(value: T): Result<T, never> {
return { ok: true, value };
}
function Err<E>(error: E): Result<never, E> {
return { ok: false, error };
}Patrones Universales
Patrón 1: Circuit Breaker
Previene fallos en cascada en sistemas distribuidos.
class CircuitState(Enum):
CLOSED = "closed" # Operación normal
OPEN = "open" # Fallando, rechaza requests
HALF_OPEN = "half_open" # Probando si se recuperó
class CircuitBreaker:
def __init__(self, failure_threshold: int = 5, timeout: timedelta = timedelta(seconds=60)):
self.failure_threshold = failure_threshold
self.timeout = timeout
self.state = CircuitState.CLOSED
def call(self, func):
if self.state == CircuitState.OPEN:
if datetime.now() - self.last_failure_time > self.timeout:
self.state = CircuitState.HALF_OPEN
else:
raise Exception("Circuit breaker está OPEN")
# ... implementación completaPatrón 2: Agregación de Errores
Recolecta múltiples errores en lugar de fallar en el primero.
Patrón 3: Degradación Elegante
Proporciona funcionalidad de fallback cuando ocurren errores.
def with_fallback(primary, fallback, log_error=True):
"""Intenta función primaria, hace fallback en error."""
try:
return primary()
except Exception as e:
if log_error:
logger.error(f"Función primaria falló: {e}")
return fallback()Mejores Prácticas
- Falla Rápido: Valida input temprano, falla rápido
- Preserva Contexto: Incluye stack traces, metadata, timestamps
- Mensajes Significativos: Explica qué pasó y cómo arreglarlo
- Loggea Apropiadamente: Error = log, fallo esperado = no spamear logs
- Maneja al Nivel Correcto: Captura donde puedas manejar significativamente
- Limpia Recursos: Usa try-finally, context managers, defer
- No Tragues Errores: Loggea o re-lanza, no ignores silenciosamente
Errores Comunes a Evitar
- Capturar Demasiado Amplio:
except Exceptionoculta bugs - Bloques Catch Vacíos: Tragarse errores silenciosamente
- Loggear y Re-lanzar: Crea entradas de log duplicadas
- No Limpiar: Olvidar cerrar archivos, conexiones
- Mensajes Pobres: "Ocurrió error" no es útil
Créditos
🚀 Compilado y Traducido por 100x — Agentes de IA para empresas que quieren crecer 100x.
📚 Más skills y tutoriales en github.com/agentes100x/agentes-100x
💼 ¿Quieres que implementemos agentes en tu empresa? Contáctanos
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

