Loading...
Loading...
Found 8 Skills
Analyze implementation details, trace data flow, and explain technical workings with precise file:line references. Use when you need to understand HOW code works.
Prime a codebase by reading every source file in full. Use when starting work on a new or unfamiliar project, or when the user asks to "learn the codebase", "read the codebase", "prime", or "get up to speed".
Search Sourcegraph-indexed codebases for patterns, examples, and system understanding. Triggers on implementation questions, debugging, or "how does X work" queries.
Conduct targeted code exploration on a repository, and document the process of "Asking Questions → Reading Code → Reaching Conclusions" as searchable evidence for direct reuse when similar questions arise next time. There are three types: question (investigate code around a specific problem and provide conclusions), module-overview (organize the structure, boundaries, entry points, and dependencies of a module), spike (conduct lightweight technical exploration of multiple possible directions without making final decisions). Trigger scenarios: When users say "Let's explore first", "How is X implemented in this repository", "Quickly get familiar with this module", "Archive the exploration results". For the distinction from learning / tricks / decisions, refer to the root skill `easysdd`.
Explain how code works in detail. Use when trying to understand unfamiliar code, complex logic, or system architecture.
Explain code in detail - what it does, how it works, and why. Use when you need to understand unfamiliar code or explain code to others.
Generates interactive codebase quizzes to test understanding of architecture, patterns, and implementation details. Configurable by card count (fewer, standard, more) and difficulty (easy, medium, hard). Use when asked to quiz me, test my knowledge, create flashcards, generate codebase questions, or run a code quiz.
Use this when you are exploring the codebase. It lets you ask the AI who wrote code questions about how things work and why they chose to build things the way they did. Think of it as asking the engineer who wrote the code for help understanding it.