smgrep
Semantic code search using natural language queries. Use when users ask "where is X implemented", "how does Y work", "find the logic for Z", or need to locate code by concept rather than exact text. Returns file paths with line numbers and code snippets.
What this skill does
## When to Use Use this to find code by **concept** or **behavior** (e.g., "where is auth validated", "how are plugins loaded"). *Note: This tool prioritizes finding the right files and locations in the code. Snippets are truncated (max 16 lines) and are often just previews.* Example: ```bash smgrep "how are plugins loaded" smgrep "how are plugins loaded" packages/transformers.js/src ``` ## Strategy for Different Query Types ### For **Architectural/System-Level Questions** (auth, LSP integration, file watching) 1. **Search Broadly First:** Use a conceptual query to map the landscape. * `smgrep "authentication authorization checks"` 2. **Survey the Results:** Look for patterns across multiple files: * Are checks in middleware? Decorators? Multiple services? * Do file paths suggest different layers (gateway, handlers, utils)? 3. **Read Strategically:** Pick 2-4 files that represent different aspects: * Read the main entry point * Read representative middleware/util files * Follow imports if architecture is unclear 4. **Refine with Specific Searches:** If one aspect is unclear: * `smgrep "session validation logic"` * `smgrep "API authentication middleware"` ### For **Targeted Implementation Details** (specific function, algorithm) 1. **Search Specifically:** Ask about the precise logic. * `smgrep "logic for merging user and default configuration"` 2. **Evaluate the Semantic Match:** * Does the snippet look relevant? * **Crucial:** If it ends in `...` or cuts off mid-logic, **read the file**. 3. **One Search, One Read:** Use smgrep to pinpoint the best file, then read it fully. ## Output Format Returns: `path/to/file:line [Tags] Code Snippet` - `[Definition]`: Semantic search detected a class/function here. High relevance. - `...`: **Truncation Marker**. Snippet is incomplete—use `read_file` for full context. ## Tips - **Trust the Semantics:** You don't need exact names. `smgrep "how does the server start"` works better than guessing `smgrep "server.init"`. - **Watch for Distributed Patterns:** If results span 5+ files in different directories, the feature is likely architectural—survey before diving deep. - **Scope When Possible:** Use path constraints to focus: `smgrep "auth" src/server/` - **Don't Over-Rely on Snippets:** For architectural questions, snippets are signposts, not answers. Read the key files. - **"Still Indexing...":** If you see this, please stop, alert the user that the index is ongoing and ask them if they wish to proceed. Results will be partial until the index is complete.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.