Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Discussion options

Hey everyone 👋

I just submitted PR #676 adding a Context Engineering collection — a set of tools focused on a simple idea: Copilot's output is only as good as the context it receives.
challenges:
The relevant files weren't open
The project structure obscures intent
Multi-file changes are requested without the full picture

What This Collection Includes

Component | What It Does -- | -- Context Architect (agent) | Before touching code, maps all affected files, traces dependencies, checks for patterns, and plans the sequence of changes Context Map (prompt) | Generates a structured table of files to modify, dependencies, test coverage, and risk assessment before any change What Context Do You Need? (prompt) | When Copilot gives a generic answer, this asks it to explicitly list the files it needs to see Refactor Plan (prompt) | For multi-file refactors — produces phased execution plans with verification steps and rollback procedures Context Engineering (instructions) | Repo-wide guidelines: use descriptive paths, keep related files open, prefer explicit types, add a COPILOT.md
You must be logged in to vote

Replies: 0 comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant
Morty Proxy This is a proxified and sanitized view of the page, visit original site.