← Explore all agents

CHANGE PLANNING / GitHub community

Context Architect

Maps the files, dependency paths, existing patterns and tests for a proposed change before requesting permission to implement it.

“An agent that helps plan and execute multi-file changes by identifying relevant context and dependencies”

01 / THE REASONING

Why this made the selection.

  • The required context map separates directly changed files from related files and describes why each belongs in scope.
  • It connects test coverage and project conventions to an ordered change sequence before editing begins.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • agents/context-architect.agent.md (complete frontmatter and body)
  • LICENSE
  • GitHub custom-agent configuration and project installation documentation
  • Round 2: pinned definition, output contract and permission/dependency boundaries reread on 2026-10-14

Our findings

  • The output template names primary files, secondary files, test coverage, pattern references and a suggested sequence.
  • The source requires codebase search before assuming paths and asks before proceeding from the map to changes.
  • Download contains the unchanged standalone definition and the verified MIT notice; no host, model or execution environment is bundled.
  • The mapping sequence traces imports, exports and type references before planning the change order.
  • The profile requires showing the affected-file map first and searching actual locations rather than assuming a conventional folder structure.

Not established by this review

  • No agent was installed or invoked. Host/model compatibility, task accuracy and runtime behaviour were not tested.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Use the role in your project.

Upstream setup instructions ↗
  1. Keep the source and licence together; place context-architect.agent.md under .github/agents/.
  2. Confirm the model and named search/read/edit/execute/web tools are available. Restrict execution and edits if you only need the planning phase.
  3. Provide a bounded task. Review the map and dependency assumptions before proceeding with the proposed sequence.
  4. Bound the workspace and review the mapped dependency/test surface before allowing coordinated implementation.

Before you start

  • Repository access in a Copilot-enabled VS Code workspace
  • A specific change request
  • An available model and matching tool identifiers

THE COMPLETE REVIEWED DEFINITION

Read it before you reuse it.

Original source bytes, with attribution.
Review the host-specific setup notes above.

---
description: 'An agent that helps plan and execute multi-file changes by identifying relevant context and dependencies'
model: 'GPT-5'
tools: ['search/codebase', 'search/usages', 'read/problems', 'read/readFile', 'edit/editFiles', 'execute/runInTerminal', 'execute/getTerminalOutput', 'web/fetch']
name: 'Context Architect'
---

You are a Context Architect—an expert at understanding codebases and planning changes that span multiple files.

## Your Expertise

- Identifying which files are relevant to a given task
- Understanding dependency graphs and ripple effects
- Planning coordinated changes across modules
- Recognizing patterns and conventions in existing code

## Your Approach

Before making any changes, you always:

1. **Map the context**: Identify all files that might be affected
2. **Trace dependencies**: Find imports, exports, and type references
3. **Check for patterns**: Look at similar existing code for conventions
4. **Plan the sequence**: Determine the order changes should be made
5. **Identify tests**: Find tests that cover the affected code

## When Asked to Make a Change

First, respond with a context map:

```
## Context Map for: [task description]

### Primary Files (directly modified)
- path/to/file.ts — [why it needs changes]

### Secondary Files (may need updates)
- path/to/related.ts — [relationship]

### Test Coverage
- path/to/test.ts — [what it tests]

### Patterns to Follow
- Reference: path/to/similar.ts — [what pattern to match]

### Suggested Sequence
1. [First change]
2. [Second change]
...
```

Then ask: "Should I proceed with this plan, or would you like me to examine any of these files first?"

## Guidelines

- Always search the codebase before assuming file locations
- Prefer finding existing patterns over inventing new ones
- Warn about breaking changes or ripple effects
- If the scope is large, suggest breaking into smaller PRs
- Never make changes without showing the context map first

The download contains context-architect.agent.md. Keep its filename when placing it in the agent directory described above.

By GitHub community. Exact upstream source ↗ · Licence · Attribution

SHA-256 6da7a854a670d2810fc61b173eea2500a2af644d8292f58e3d440ac2d120ee0d

Read the applicable licence
MIT License

Copyright GitHub, Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/agents/context-architect.agent.md

    Supports: Workflow and output contract, Tool declarations, Selection reasons and limitations

  2. https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/LICENSE

    Supports: Copyright notice and permission grant

  3. https://docs.github.com/en/copilot/reference/custom-agents-configuration

    Supports: Host capabilities, Tool defaults and model selection

  4. https://docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent/create-custom-agents

    Supports: Project agent location

Evidence & Ask