Loading...
Loading...
Found 64 Skills
Maps questions to the optimal tldr command. Use this to pick the right layer
Explore and analyze GitHub repositories related to a research topic. Reads deep-research output, discovers repos from multiple sources, deeply analyzes code, and produces integration blueprints.
Cognitive science-based deep source code understanding assistant (Chinese improved version). Supports three analysis modes: Quick (overview), Standard (comprehension), Deep (mastery, automatically uses parallel processing for large projects). Integrates elaborative interrogation, self-explanation testing, and retrieval practice to help truly understand and master code.
Microscopic deconstruction and exhaustive analysis of code, systems, documents, or concepts. Breaks subjects into atomic components, examines every facet, and produces encyclopedic reports. Use when deep understanding is needed before making changes, analyzing unfamiliar codebases, or producing thorough technical documentation. Triggers on "심층 분석", "deep dive", "분석해줘", "해부", "deconstruct", "뜯어봐", "thoroughly analyze", "코드 분석".
Generate feature specifications by analyzing existing source code.
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"
Explain how something works in this codebase by exploring code and producing a clear architectural explanation. Optionally critique the architecture for issues.
Generate comprehensive scientific research-style documentation for completed coding projects. Use when the user requests project documentation, a technical breakdown, a study paper, a lecture document, or wants to understand everything about a project they just built. Triggers include phrases like "document this project," "create a study paper," "explain everything we did," "write up the full breakdown," "scientific documentation," or "I want to learn from this project." Produces formal Word documents (.docx) with academic structure, beginner-friendly explanations, and exhaustive code analysis.
Extract entities and relations from source files to build a knowledge graph
Analyze codebase for GoF design patterns - detection, suggestions, evaluation with stack-aware adaptations
Use when answering complex questions about a codebase that require exploring multiple areas or understanding how components connect - coordinates parallel sub-agents to locate, analyze, and synthesize findings
Use when mapping code paths, entrypoints, and likely hot files before profiling.