Loading...
Loading...
Found 27 Skills
Use GitHits CLI for canonical open-source examples, indexed source, docs, grep, file listing, and code navigation. Activate when verifying library behavior from source or examples. For metadata, vulnerabilities, dependency graphs, or changelogs, use githits-package instead.
This skill should be used when finding, tracing, or understanding code in a repository with SymDex available. Trigger it for requests like "where is this defined?", "who calls this?", "what route handles this path?", "show me the file outline", "search this codebase by intent", or any task that would otherwise rely on broad Read/Grep/Glob exploration.
Use this skill when > Request a broader architectural perspective when navigating unfamiliar code sections. Maps all relevant modules, identifies caller relationships and dependencies, and uses domain-specific vocabulary. Use when encountering unfamiliar code or needing to understand how a component integrates with the larger system.
Use when the user needs to search or navigate code with Sourcegraph MCP tools. Provides disciplined search workflows for finding implementations, understanding systems, debugging issues, fixing bugs, and reviewing code.
Thorough codebase search
Read GitHub repos the RIGHT way - via gitmcp.io instead of raw scraping. Why this beats web search: (1) Semantic search across docs, not just keyword matching, (2) Smart code navigation with accurate file structure - zero hallucinations on repo layout, (3) Proper markdown output optimized for LLMs, not raw HTML/JSON garbage, (4) Aggregates README + /docs + code in one clean interface, (5) Respects rate limits and robots.txt. Stop pasting raw GitHub URLs - use this instead.
Search the code knowledge graph by function, class, or type using FTS5 full-text search.
Runs tilth CLI for structural code navigation — reads files with smart outlining, searches symbols/text/regex, finds files by glob, and maps codebases. Use instead of read/grep/find for all source code exploration.
Navigate unfamiliar code using GitNexus knowledge graph
Add or refresh a fixed 20-line file-header comment that summarizes a source file and indexes key classes/functions with line-number addresses. Use when annotating large codebases for fast navigation, onboarding, refactors, or when you want LLMs/humans to locate relevant symbols quickly without reading entire files.
Use when you need to ask questions about a codebase or understand code using a knowledge graph
Open a known repository file, source line, or source range in a Herdr Files pane for the user to inspect.