What is the purpose of this skill?

To prompt Copilot to declare the files it needs before answering.

What output will I see?

A structured set of sections: Must See, Should See, Already Have, and Uncertainties.

Can I update context after initial response?

Yes—provide new files or ask Copilot to re-evaluate; iteration is supported.

what-context-needed

npx machina-cli add skill github/awesome-copilot/what-context-needed --openclaw

Files (1)

SKILL.md

881 B

What Context Do You Need?

Before answering my question, tell me what files you need to see.

My Question

Instructions

Based on my question, list the files you would need to examine
Explain why each file is relevant
Note any files you've already seen in this conversation
Identify what you're uncertain about

Output Format

## Files I Need

### Must See (required for accurate answer)
- `path/to/file.ts` — [why needed]

### Should See (helpful for complete answer)
- `path/to/file.ts` — [why helpful]

### Already Have
- `path/to/file.ts` — [from earlier in conversation]

### Uncertainties
- [What I'm not sure about without seeing the code]

After I provide these files, I'll ask my question again.

Source

git clone https://github.com/github/awesome-copilot/blob/main/plugins/context-engineering/skills/what-context-needed/SKILL.md

View on GitHub

Overview

What Context Do You Need? prompts Copilot to declare the exact files required before answering, explains why each file matters, notes any files already seen, and highlights uncertainties. This focused context keeps answers precise and minimizes guesswork.

How This Skill Works

When you ask a question, Copilot returns a structured list of file categories: Must See, Should See, Already Have, and Uncertainties, with explanations for why each file is needed. After you provide the listed files, you can re-ask your question for a focused response.

When to Use It

When you need a precise answer that depends on specific code files
Before debugging to confirm the scope and required context
When you want to avoid guessing about hidden or optional files
During refactoring to bound analysis to relevant sources
In code reviews to ensure discussion covers only necessary files

Quick Start

Step 1: State your question clearly
Step 2: Ask Copilot to list the files it needs to answer
Step 3: Review the generated Must See/Should See/Already Have/Uncertainties and re-ask with the files

Best Practices

Ask clearly for which files are required for the answer
Explain why each file is relevant to the question
Note files you've already seen to avoid duplication
Be mindful of sensitive or private files and restrict exposure as needed
Iterate by updating the file list if the answer changes

Example Use Cases

Bug fix: request must-see files like src/utils/logger.ts and src/api/client.ts with reasons
Refactor: identify config and build files (e.g., tsconfig.json, webpack/config) to inform the analysis
Security review: focus on config, credentials handling, and access control files
Performance tuning: target critical path modules and profiling data
API integration: specify schema definitions, adapters, and client implementations

Frequently Asked Questions

Add this skill to your agents