.png){kind=small}
@workspace: Asking Questions Across an Entire Repo
Use workspace-scoped context effectively — when, latency, what it sees.
What You Will Learn
- Use @workspace for repo-wide questions.
- Understand latency trade-offs.
- Recognize what @workspace can/can't see.
- Scope queries effectively.
- Combine with file attachments.
Why This Matters
Beginner @workspace (BE-10) is 'ask a question'. Intermediate @workspace is knowing when to use it (cross-file questions), when not (single-file), and how to scope for precision without losing breadth.
Concept Explained
@workspace indexes your repo and includes relevant files in context. It's powerful for architecture, dependency, and cross-file questions, but adds latency and consumes budget.
How It Works
Type @workspace followed by your question. Copilot indexes the repo (cached after first use), finds relevant files, includes them in context. Latency: first call slow, subsequent faster.
Step-by-Step Tutorial
1. Identify cross-file questions
'How does X connect to Y?', 'Where is Z used?', 'What's the data flow?'2. Use @workspace
Type @workspace + your question. Wait for indexing on first call.3. Be specific
'How does the auth middleware connect to the user service?' beats 'How does auth work?'4. Combine with attachments
Attach key files explicitly for precision; use @workspace for breadth.5. Recognize limits
@workspace sees committed files, not unsaved buffers or untracked files.Real-World Example
A new hire used @workspace to map a 50-file module: 'What files are involved in user authentication? List them with one-line descriptions.' Got a structured map in 30 seconds. Then asked: 'How does a login request flow through these files?' Got a step-by-step trace. Onboarding time: 90 minutes instead of 2 days.
Example Prompts / Commands / Code
# Architecture:
@workspace What files are involved in the authentication system? List them with one-line descriptions.
# Data flow:
@workspace Trace a login request from the API endpoint through to the database. List each file and function involved.
# Dependencies:
@workspace Which files import from 'lib/auth'? List them.
# Impact analysis:
@workspace If I change the signature of function X in file Y, what files would be affected?
# Finding patterns:
@workspace Where in the codebase do we use the Repository pattern? List examples.
Common Mistakes
- Using @workspace for single-file questions — adds latency without value.
- Vague questions — produces vague answers.
- Forgetting @workspace doesn't see unsaved/untracked files.
- Not combining with file attachments for precision.
Best Practices
- Use @workspace for cross-file questions only.
- Be specific: 'how does X connect to Y?' beats 'how does X work?'.
- Combine with explicit file attachments for precision.
- Recognize @workspace sees committed files only.
- First call is slow (indexing); subsequent calls faster.
Troubleshooting
| Problem | How to Fix |
|---|---|
| @workspace is slow | Repo is large. Narrow scope by attaching specific files instead. |
| Answer is generic | Be more specific. Attach key files explicitly. |
Practical Exercise
Your Turn
Pick a project you know well. Use @workspace to ask 3 architecture questions. Verify the answers against your knowledge. Did @workspace surface anything you didn't know?
Professional Challenge
Use @workspace to map a module you don't know well. Produce a one-page architecture summary. Verify by reading the actual code.
Key Takeaways
- @workspace indexes your repo for cross-file questions.
- Use for architecture, dependencies, data flow.
- Be specific; vague questions get vague answers.
- Combine with file attachments for precision.
- First call slow (indexing); subsequent faster.
Frequently Asked Questions
Does @workspace see unsaved files?
How large a repo can @workspace handle?
Further Reading
Official References
SEO Metadata
SEO title: @workspace: Asking Questions Across an Entire Repo
Meta description: Use workspace-scoped context effectively — when, latency, what it sees.
Primary keyword: @workspace
Secondary keywords: @workspace: asking questions across an entire repo
Search intent: Informational
URL slug: /workspace-scoped-questions-copilot
Categories: AI Tools, GitHub Copilot
Tags: GitHub Copilot, Intermediate, @workspace, Workspace, Prompting, IMCSEIAN, Tutorial, IMCSEIAN
Featured image concept: IMCSEIAN lesson card for @workspace: Asking Questions Across an Entire Repo
Comments
Comments
Post a Comment