context-research

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 1. **Start broad**: Use `jbcontext search` with general terms to understand the landscape 2. **Narrow down**: Add path filters (`-p`) once you identify relevant directories 3. **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" ```