context-research

Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

You need to gather all context for task $ARGUMENTS thoroughly.

When to Use

Understanding unfamiliar codebases or locating specific functionality
Finding implementations, definitions, or usage patterns
Identifying code related to specific features or concepts
Before making changes to understand the context and impact

Tools Available

`jbcontext search`

Semantic code search that finds code by meaning, not just exact keywords.

bash

jbcontext search "<descriptive query>" [path]
jbcontext search -p <path> "<query>"  # <path> must be relative to the project root

Query Tips:

Be descriptive: "function that validates user email addresses" > "email"
Include context: "error handling middleware for HTTP requests with logging"
Specify what you're looking for: "React component that renders a modal dialog"

Research Workflow

Start broad: Use jbcontext search with general terms to understand the landscape
Narrow down: Add path filters (-p) once you identify relevant directories
Read the code: Once you find relevant files, read them to understand the details

Example Session

bash

# Find authentication-related code
jbcontext search "user authentication login"

# Narrow to specific directory
jbcontext search -p src/auth "JWT token validation"

context-search

Semantic code search for discovering and understanding code by meaning rather than keywords.\n- Use this skill when you need to find code whose location you don't already know - e.g., when the task asks 'where is X', 'how does Y work', or describes behavior or intent without naming exact symbols.\n- When not to use: if you already know the relevant file, class, or symbol (use direct navigation or keyword search instead), or for non-code-discovery tasks such as git operations, builds, tests, or reviewing an existing diff.

installations

GitHub Stars

Mis à jour

28 août

1 Fichiers

Voir les détails →