root-cause-tracing

Name: root-cause-tracing
Rating: 5 (3 reviews)
Author: carlopezzuto

Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

3stars

Updated 3 months ago

View on GitHub ↗License: MIT

How to add

/plugin marketplace add carlopezzuto/agents

The exact command may vary by repository. Check the README on GitHub.

For the skill author

Drop this on your repo README

Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.

[![Listada na Skillteca](https://www.skillteca.com.br/api/badge/root-cause-tracing-carlopezzuto/svg)](https://www.skillteca.com.br/skills/root-cause-tracing-carlopezzuto?utm_source=badge&utm_medium=readme&utm_campaign=badge)

Related skills

See all in Dados e Análise →

xlsx

143.8k

Use this skill for any task involving spreadsheet files as primary input or output, such as opening, reading, editing, fixing, creating, or converting .xlsx, .xlsm, .csv, or .tsv files.

Dados e Análise#xlsxby anthropics

mem-search

79.7k

Searches claude-mem's persistent cross-session memory database. Use this to answer questions about previous solutions or retrieve work from past sessions.

Dados e Análise#aiby thedotmack

weekly-digests

79.7k

Generates a week-by-week narrative digest of a project's Claude-mem timeline, splitting it into ISO-week files and using subagents to produce weekly chapters. Ideal for "weekly digests" or "narrative chapters" of a project's history.

Dados e Análise#aiby thedotmack

how-it-works

79.7k

This skill explains how claude-mem captures observations, when memory injection occurs, and where its data is stored.

Dados e Análise#aiby thedotmack

Category alert

Get new Dados e Análise skills every Monday

One short email with only the new Dados e Análise skills. 4 minutes of reading, no spam, unsubscribe with one click.

You confirm your email on the first send. No spam. Unsubscribe with one click.

Root Cause Tracing

Overview

Bugs often manifest deep in the call stack (git init in wrong directory, file created in wrong location, database opened with wrong path). Your instinct is to fix where the error appears, but that's treating a symptom.

Core principle: Trace backward through the call chain until you find the original trigger, then fix at the source.

When to Use

digraph when_to_use {
    "Bug appears deep in stack?" [shape=diamond];
    "Can trace backwards?" [sh

[Description truncada. Veja o README completo no GitHub.]

ShareX LinkedIn

Comments · No comments

No comments yet. Be the first.