Root cause tracing
Skill lubochka/xiigen-mvp-engine/.claude/skills/universal/root-cause-tracing
Self-building AI code generation engine that generates application flows instead of implementing them. AGPL-3.0.
npx -y skills add lubochka/xiigen-mvp-engine --skill root-cause-tracingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 13 days oldThe repository was created 13 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.8 KB, as published. Nobody here has run it
Root Cause Tracing
Purpose
Use this to avoid treating symptoms as causes during bug fixes, test failures, data issues, and integration problems.
When to Use
Invoke when behavior is wrong, tests fail, data is missing, logs disagree with expectations, or multiple fixes have not resolved the issue.
Actions
- State the symptom precisely with observed evidence.
- Trace backward through inputs, transformations, dependencies, configuration, persistence, and outputs.
- Compare broken behavior with a nearby working example in the same project.
- Form one hypothesis at a time and test it with the smallest reliable check.
- Only fix after the root cause is supported by evidence.
XIIGen Adaptation
- Common XIIGen trace points include DataProcessResult<T> status propagation, Promise/AbortSignal flow where locally present, NestJS provider or injection-token wiring, config helper defaults, structured logging evidence, Record<string, unknown>/unknown serialization, and buildSearchFilter/buildSearchFilterFlat empty-value behavior.
- Use local XIIGen code as the reference, not source project internals.
Avoid
- Do not stack speculative fixes.
- Do not stop at the first visible exception if upstream data or config caused it.
- Do not import source architecture, algorithms, design patterns, training, DPO, source domains, source classes, or source-specific paths.
Completion Signal
- The cause is evidence-backed, the fix targets that cause, and verification checks the original symptom.