Custom instructions for Copilot #169109
Replies: 5 comments
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
Im having the same problem in VSCode (ps. it was working fine earlier this week). |
Beta Was this translation helpful? Give feedback.
-
|
Now, Im having the same problem in VSCode and JetBrains IDEs. Is this a bug or is there no missing feature? |
Beta Was this translation helpful? Give feedback.
-
|
I've got a similar issue, but only with Copilot Code Review on GitHub.com, it works fine in VS Code. # GitHub Copilot Code Review Instructions
The goal of the Copilot pull request review is to validate if the PR is ready to review by a human.
## Core Rules
**MANDATORY REQUIREMENTS - THESE ARE NOT OPTIONAL:**
- **ALWAYS use the Review Summary Format** - You MUST use the exact **Review Summary Format** specified at the end of these instructions for every review
- **NEVER approve a PR** - You can leave comments or request review, but NEVER EVER approve
## Review Process
1. **Check build status and merge conflicts first** - Request changes for blocking technical issues
- Use `mcp_github_get_pull_request` to check if `mergeable` is `true` = All checks passed, no conflicts ✅
2. **Check for missing tests** - If PR adds new functionality without corresponding test files, request changes
- Use `mcp_github_get_pull_request_files` to identify all test files and examine their patterns
5. **Comment on PR** - Post a comment with your review summary, following the **Review Summary Format**
*Review Summary Format**: Keep main review comments under 10 lines maximum. Use format:
**Status**: ✅ READY FOR REVIEW / ❌ CHANGES REQUESTED
**Build/Merge**: [status]
**Tests**: [test file count] - [critical violations if any]
|
Beta Was this translation helpful? Give feedback.
-
|
We are having the same issue, instructions file doesn't seem to be recognized by any of the Github Copilot tools (PR Review, Agent, Chat, etc). Weirdly, when I ask Copilot to create a PR with custom instructions then it recognizes the file already exists but the file wasn't attached as context to the original ask. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Copilot Feature Area
Copilot in GitHub
Body
Hi, I added custom instructions file for Copilot, in order to have specific review instructions.

I did exactly as explained here but it doesn't seem to work.
You can see in the attached image the file and the Copilot response without the instructions
I'll be glad for help what I'm missing
Beta Was this translation helpful? Give feedback.
All reactions