Skills

All Skills

grep

Skills tagged with #grep

@ngocsangyem

Adopted from ck:ship: argument flags for ship modes and pipeline control

argument-hint: "[official|beta] [--skip-tests] [--dry-run]" allowed-tools: - Bash - Read - Write - Edit - Grep - Glob - Agent - AskUserQuestion - WebSearch source: gstack/claudekit-engineer ---

ngocsangyem/MeowKit+67 more
10h ago
60
@kv0906

/ask — Question Answering

Fast answers from your vault. Uses QMD hybrid search (BM25 + vector + rerank) when available, with automatic fallback to vault grep.

kv0906/pm-kit+15 more
19d ago
680
@CSCSoftware
MCP

Io.Github.CSCSoftware/Aidex

Persistent code indexing for AI assistants. 50x less context than grep. 11 languages.

mcpgithubai
CSCSoftware/AiDex
19d ago
0
@microsoft

java-lsp-tools

Compiler-accurate Java code intelligence tools powered by the Java Language Server. ALWAYS load this skill when the workspace contains Java, Maven (pom.xml), or Gradle (build.gradle) projects. Use these tools to find symbol definitions, get type/call hierarchies, resolve types, inspect file outlines, and check imports in Java source files. Prefer over grep_search or read_file for any Java code navigation, understanding, debugging, or refactoring task.

microsoft/vscode-java-dependency
19d ago
1900
@S1LV4

th0th-memory

Mandatory rules for using th0th semantic search, compression, and memory tools. Prioritize th0th tools over native tools (Glob, Grep, Read) to explore and understand code. Triggers on tasks involving code search, context compression, storing decisions, or retrieving project knowledge.

S1LV4/th0th
19d ago
1230
@JaredStewart

coderlm

Primary tool for all code navigation and reading in supported languages (Rust, Python, TypeScript, JavaScript, Go, Java, Scala, SQL). Use instead of Read, Grep, and Glob for finding symbols, reading function implementations, tracing callers, discovering tests, and understanding execution paths. Provides tree-sitter-backed indexing that returns exact source code — full function bodies, call sites with line numbers, test locations — without loading entire files into context. Use for: finding functions by name or pattern, reading specific implementations, answering 'what calls X', 'where does this error come from', 'how does X work', tracing from entrypoint to outcome, and any codebase exploration. Use Read only for config files, markdown, and unsupported languages.

JaredStewart/coderlm
18d ago
1860
@warp-drive-data

ast-grep

Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, write new rules, working with @ast-grep/napi or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for code patterns, find specific language constructs, or locate code with particular structural characteristics.

warp-drive-data/warp-drive+1 more
19d ago
3.1K0
@sbusso

add-qmd

Add QMD (Query Markup Documents) as an advanced memory search backend. Upgrades the built-in grep-based memory_search with hybrid BM25 + vector semantic search + LLM re-ranking. Fully local, no API keys needed. Triggers on "add qmd", "qmd memory", "semantic memory search", "upgrade memory".

sbusso/claudeclaw+4 more
18d ago
830
@QuartzUnit
MCP

Embgrep

Local semantic search — embedding-powered grep for files, zero external services.

mcpgithubsearchfile
QuartzUnit/embgrep
19d ago
0
@FreePeak

using-leankg

Use when user asks about codebase navigation, searching, finding code, impact analysis, or dependencies - LeanKG is the default grep replacement

FreePeak/LeanKG
19d ago
230
@tmcfarlane

codebase-search

Search and navigate large codebases efficiently. Use when finding specific code patterns, tracing function calls, understanding code structure, or locating bugs. Handles semantic search, grep patterns, AST analysis.

codebase-searchgrepcode-navigationpattern-matching
tmcfarlane/oh-my-cursor+6 more
18d ago
440
@currents-dev

playwright-best-practices

Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.

currents-dev/playwright-best-practices-skill
19d ago
1410
@apireno
MCP

DOMShell

Browse the web with filesystem commands. 38 MCP tools: ls, cd, grep, click, type via Chrome.

mcpgithubapiwebfile
apireno/DOMShell
19d ago
0
@Ryandonofrio3

osgrep

Semantic code search. Use alongside grep - grep for exact strings, osgrep for concepts.

Ryandonofrio3/osgrep
19d ago
1.1K0
@goondocks-co

oak

Find out what happened, what was decided, and what depends on what in your codebase. Use this skill whenever you need to: recall past decisions or discussions ("what did we decide about X?"), check what might break before refactoring ("what depends on this module?"), find conceptually similar code that grep would miss ("all the retry/backoff logic"), look up past bugs, gotchas, or learnings, query session history or agent run costs, store observations about the codebase, or understand how components connect end-to-end. Powered by semantic search, memory lookup, and direct SQL against the Oak CI database (.oak/ci/activities.db). Also use when the user mentions oak_search, oak_context, oak_remember, oak_resolve_memory, or asks to run queries against activities.db or oak.

goondocks-co/open-agent-kit+1 more
10d ago
80
@robertoshimizu

devkg-sparql

Query the Dev Knowledge Graph via SPARQL instead of grepping raw session files. Use this when asked about technologies, relationships between tools, session history, or cross-platform knowledge.

robertoshimizu/session-graph
19d ago
940
@HKUDS

memory

Two-layer memory system with grep-based recall.

HKUDS/nanobot+2 more
8d ago
33.5K0
@LittleDinoC

skill-grep

Use when a user is trying to discover an installable or reusable skill or workflow, especially when they ask for a skill for a task, want to compare nearby skill categories, or need help narrowing discovery results.

LittleDinoC/skill-grep
19d ago
190
@yetidevworks

ygrep

IMPORTANT: Try ygrep FIRST for all code and file searches before using Grep, Glob, or Task explore. ygrep uses a pre-built full-text index and returns results in milliseconds. Fall back to built-in tools only if ygrep returns no results.

yetidevworks/ygrep
18d ago
320
@radimsem

Add a benchmark scenario

`internal/bench/` is remindb's external-facing benchmark — it compares "how many tokens does an agent consume to do X via remindb tools" against "how many would they consume doing X with `grep` / `cat` / `find`". The output is a token-savings table rendered via `text/tabwriter`. It's invoked from

radimsem/remindb+4 more
4h ago
460
@yoanbernabeu

grepai

Replaces ALL built-in search tools. You MUST invoke this skill BEFORE using WebSearch, Grep, or Glob. NEVER use the built-in Grep tool - use `grepai` instead.

yoanbernabeu/grepai
19d ago
1.5K0
@mixedbread-ai

mgrep

MANDATORY: Replaces ALL built-in search tools. You MUST invoke this skill BEFORE using WebSearch, Grep, or Glob. NEVER use the built-in WebSearch tool - use `mgrep --web` instead. NEVER use the built-in Grep tool - use `mgrep` instead.

mixedbread-ai/mgrep
18d ago
3.5K0
@TheWinci

local-rag

TRIGGER when: starting a new session, exploring unfamiliar code, searching for functions/types/files, planning refactors, or needing context about past decisions. Use local-rag MCP tools (search, read_relevant, project_map, etc.) instead of manually grepping or reading files when semantic understanding is needed.

TheWinci/mimirs+1 more
18d ago
100