GitHub Copilot: Initialize copilot-instructions.md Before Starting Agentic Tasks

[sharpninja]

Select Topic Area

Product Feedback

Copilot Feature Area

Visual Studio

Body

GitHub Copilot: Initialize copilot-instructions.md Before Starting Agentic Tasks

Problem Statement

GitHub Copilot should not begin performing agentic tasks before completely ingesting and processing the copilot-instructions.md file and establishing all guardrails defined within it.

Problem Observed

In a project with comprehensive .github/copilot-instructions.md file defining specific requirements, Copilot:

• Started performing tasks immediately without reading the instructions file
• Violated defined guardrails such as using inline PowerShell commands instead of creating .ps1 script files first
• Did not create Copilot Session Logs for significant work
• Ignored specific code style and documentation requirements
• Required multiple corrections from the user to align with project standards
• Created inconsistent deliverables early in the session

Expected Behavior

Copilot should:

1. Detect copilot-instructions.md files in project repositories
2. Read and parse the complete instructions file
3. Extract and set up guardrails
4. Establish execution constraints before beginning any task
5. Acknowledge the instructions and constraints to the user
6. Validate all work against the defined standards before delivering

Real-World Example

Instructions: Do not edit files by writing powershell snippets. When executing multiline powershell statements, write the statement to a script and execute the script.

What happened: Copilot executed inline PowerShell commands instead of creating script files first. Copilot did not create session logs until explicitly corrected. User had to point out violations.

Suggested Implementation

1. Initialization Hook - Load and parse instructions at session start
2. Guardrail Enforcement - Prevent violations, suggest alternatives
3. Session Tracking - Monitor complexity, create required documentation
4. User Communication - Acknowledge rules, explain deviations

Benefits

• Consistency across all Copilot work
• Reduced need for corrections
• Better alignment with team practices
• Professional deliverables from the start

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐