Systematic debugging
Skill lubochka/xiigen-mvp-engine/.claude/skills/universal/systematic-debugging
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 systematic-debuggingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 16 days oldThe repository was created 16 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, 298 tokens by cl100k_base, as published. Nobody here has run it
Systematic Debugging
Purpose
Use this for technical failures where guessing would risk churn or regressions.
When to Use
Invoke for build errors, test failures, runtime bugs, integration failures, flaky behavior, performance surprises, or confusing generated output.
Actions
- Reproduce or isolate the failure before changing code.
- Read the full relevant error output, stack trace, logs, or failing assertion.
- Inspect recent changes and nearby working examples.
- Create one evidence-backed hypothesis and test it with one focused change or check.
- After fixing, rerun the verification that proves the original failure is gone.
XIIGen Adaptation
- For XIIGen services, inspect DataProcessResult<T> wrapping, Promise/AbortSignal behavior where locally present, NestJS provider or injection-token wiring, config helper defaults, structured logging, dynamic Record<string, unknown>/unknown payload handling, and buildSearchFilter/buildSearchFilterFlat construction when relevant.
- Scale verification to the change: targeted test, build, content check, or manual artifact review.
Avoid
- Do not guess-fix under time pressure.
- Do not bundle refactors into a bug fix.
- Do not import source architecture, algorithms, design patterns, training, DPO, source domains, source classes, or source-specific paths.
Completion Signal
- The issue is reproduced or isolated, root cause is known, the fix is focused, and verification proves the failure path is resolved.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.