baka3k

Search library/framework documentation via llms.txt (context7.com). Use for API docs, GitHub repository analysis, technical documentation lookup, latest library features.

ALWAYS activate before implementing ANY feature, plan, or fix.

Debug systematically with root cause analysis before fixes. Use for bugs, test failures, unexpected behavior, performance issues, call stack tracing, multi-layer validation, log analysis, CI/CD failures, database diagnostics, system investigation.

ALWAYS activate before fixing ANY bug, error, test failure, CI/CD issue, type error, lint, log error, UI issue, code problem.

Unified knowledge retrieval skill. Build traceable answers from git, MCP, and memory files.

Plan implementations, design architectures, create technical roadmaps with detailed phases.

Apply systematic problem-solving techniques when stuck. Use for complexity spirals, innovation blocks, recurring patterns, assumption constraints, simplification cascades, scale uncertainty.

Apply step-by-step analysis for complex problems with revision capability. Use for multi-step reasoning, hypothesis verification, adaptive planning, problem decomposition, course correction.

Fix ts_backend_analyzer.py missing --commit-sha-before/after and message-scan args

Parse and ingest source code into Neo4j and Qdrant using the Python analyzers in graph-code-tiny. Use when asked to scan repositories, build call graphs, store symbols/relations in Neo4j, push embeddings into Qdrant, tune batching/caching, or run Kotlin/Java/C#/C++/TypeScript/JavaScript/PHP/SQL/PL/SQL analyzers.