graphify-recurring-bugs

1# Graphify-Aware Recurring Bugs
2 
3## Overview
4 
5A stack trace shows where a bug surfaced, not everywhere its root cause reaches. Grepping around
6the crash site misses related call sites that share the same underlying problem — which is exactly
7how the same root cause gets logged as three unrelated "new" bugs over time. `graphify` already
8builds a queryable structural map of a codebase; this skill puts that map to work specifically
9during bug investigation, not just general code Q&A.
10 
11**Core principle:** a recurring bug should be recognized as recurring — and its known-good fix
12reused — not re-discovered as new. graphify is the linker that recalls the past occurrence;
13`KNOWN_ISSUES.md` is where the fix that worked is actually recorded.
14 
15## Gate: does this apply?
16 
17Check for `graphify-out/graph.json` at the project root before doing anything else in this skill.
18 
19- **Missing** → this skill is a complete no-op. Don't suggest building a graph mid-investigation
20  (that's a real side effect — leave it to `/craftsman:init`'s ask-first note, or to the user
21  deciding to run `graphify .` themselves). Proceed with normal root-cause investigation.
22- **Present** → continue below.
23 
24## During root-cause investigation
25 
26This slots into the evidence-gathering step of root-cause investigation (Phase 1 of the
27superpowers `systematic-debugging` skill, where that plugin is installed) — run this *before*
28falling back to raw grep:
29…