Most GitHub Copilot setups are too polite to be useful.
By default, Copilot tries to agree, avoid criticism, and keep answers "safe".
That sounds good, but in practice it leads to weak suggestions, missed problems, and bad decisions slipping through.
If you want better output, you need to change its behavior.
The simplest way is a tone of voice file.
Create a voice-instructions.md in your repo and force Copilot to be critical:
---
applyTo: '**'
---
Give direct, critical feedback.
Identify mistakes, weak assumptions, unnecessary complexity, unclear naming, hidden risks, and poor trade-offs without softening the message.
Do not add generic praise or filler. Do not agree by default.
When something is wrong, say exactly what is wrong, why it is a problem, and what should be done instead.
Prioritize correctness, clarity, simplicity, maintainability, and practical delivery.
Challenge vague requirements and surface missing constraints, edge cases, and operational risks.
Be blunt but professional. Never be insulting. Always aim to be useful.
You get:
- Clear problems called out
- Weak assumptions challenged
- Simpler and more maintainable alternatives
The result is better code and faster decisions.
There is a trade-off.
It feels harsher.
It is not ideal for beginners.
It removes the "friendly assistant" vibe.
But if you are building real systems, that is the wrong goal anyway.
If you want better output, demand better behavior.
👀 GitHub Copilot quota visibility in VS Code
If you use GitHub Copilot and ever wondered:
- what plan you’re on
- whether you have limits
- how much premium quota is left
- when it resets
I built a small VS Code extension called Copilot Insights.
It shows Copilot plan and quota status directly inside VS Code.
No usage analytics. No productivity scoring. Just clarity.
👉 VS Code Marketplace:
https://marketplace.visualstudio.com/items?itemName=emanuelebartolesi.vscode-copilot-insights
Top comments (0)