question

Name: question
Availability: InStock
Author: ggemba

Answer developer questions about codebase behavior with file:line citations.

4|3|Updated May 2, 2026

Search Tags:#static analysis #developer productivity #grep #codebase navigation #read-only #file:line citations #code q&a

Ready to run

npx skills add https://github.com/ggemba/squad-mcp --skill question-ggemba

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

Read-only code Q&A: Answers “where/how/what calls what” without changing anything in your repository.
Fast cited findings: Dispatches a code-explorer subagent to search by grep/glob/excerpts and then synthesizes an answer with file:line citations.
Configurable search depth: Uses --quick, --thorough, or the default breadth to balance speed versus coverage for tasks like tracing definitions and locating references.

Quick Start

Ask: “Where is the rate-limit middleware applied in this codebase?” and include --thorough if the initial answer is missing cross-cutting references.

Frequently Asked Questions about question

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find where a specific function is called in a large codebase?▼

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.

How does code Q&A explain how a specific feature works without modifying files?▼

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.

Can I control the search breadth when tracing definitions across large repositories?▼

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.

What is the best way to locate middleware application points in a repository?▼

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.

Are there limitations when using static analysis for codebase navigation?▼

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.