Menü
Explore and understand unfamiliar codebases using semantic code search
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Experimental jbcontext org-wide blast-radius analysis across multiple repositories. Use when Codex needs to estimate the impact of changing an API, endpoint, schema, event, shared library, config, feature flag, data model, behavior, or dependency by finding producers, consumers, owners, tests, and related repos.
Install jbcontext and complete first-time setup — login and configure agent integration. Use when `jbcontext` is not found or the user asks to install jbcontext.
Research and understand unfamiliar codebases using semantic search with `jbcontext search`
Use this skill to review code changes using semantic search to understand context and impact
Experimental jbcontext org-wide dependency search across multiple repositories. Use when need to find APIs in other repositories, or dependency configuration are used across repos for upgrades, removals, CVEs, migrations, or ownership discovery.
Experimental jbcontext org-wide semantic search across multiple repositories
| name | context-search |
| description | Explore and understand unfamiliar codebases using semantic code search |
| argument-hint | query |
Use jbcontext search to find code snippets by meaning, not just keywords.
Use it as a single semantic bootstrap when the relevant file or subsystem is unknown. Do one broad search, open and inspect at least one returned file locally, and inspect nearby code in that same directory or subsystem before any retry. If that still does not identify the needed adjacent area, do a narrowed retry with jbcontext search -p <path> ... using the directory of the best first hit.
jbcontext search "<detailed and descriptive query>"
jbcontext search "<code snippet>" # find similar snippets
jbcontext search -p <path> "<query>" # <path> must be relative to the project root
# Find authentication-related code
jbcontext search "user authentication login flow"
# Narrow to specific directory
jbcontext search -p src/auth "JWT token validation"