Answer developer questions about codebase behavior with file:line citations.
npx skills add https://github.com/ggemba/squad-mcp --skill question-ggemba
Please help me install this Agent Skill. Skill: question Source: https://github.com/ggemba/squad-mcp/tree/main/skills/question Command: npx skills add https://github.com/ggemba/squad-mcp --skill question-ggemba
When you need to understand a behavior in the codebase quickly, question mode finds the right places and explains them with precise file and line citations.
--quick, --thorough, or the default breadth to balance speed versus coverage for tasks like tracing definitions and locating references.Ask: “Where is the rate-limit middleware applied in this codebase?” and include --thorough if the initial answer is missing cross-cutting references.
High-intent search queries and answers about installing and using this skill.
Codebase navigation tools help you find where a function is called by scanning repository files with grep and tracing references. They return answers with file:line citations, ensuring you can quickly locate exact call sites without manual searching.
Code Q&A explains feature behavior by operating strictly read-only and avoiding state-mutating shell or git actions. It dispatches a subagent to search code excerpts and synthesizes an explanation with precise file:line citations for developer reference.
Yes, you can control search breadth when tracing definitions using configurable depth flags. It offers quick, default, and thorough search modes to balance speed versus coverage, allowing you to find cross-cutting references efficiently across large repositories.
The best way to locate middleware application points is using read-only code Q&A with file:line citations. It searches the codebase to answer where specific configurations are applied, and you can include a thorough flag to ensure no cross-cutting references are missed.
Limitations of static analysis for codebase navigation include balancing speed versus coverage, where quick searches might miss cross-cutting references. It operates read-only so it cannot execute code to infer runtime behavior, relying entirely on grep and glob search patterns.
jimmymalhanSearch codebase, logs, and configurations with Grep, Glob, and Read tools.
DaniloUnicamDesign probes to test runtime behavior and generate structured reports.
cwilliams5Audit query tools for accuracy, coverage gaps, and retirement candidates.
ByronWilliamsCPAQuery a codebase knowledge graph to trace calls, find dead code, and analyze dependencies.