Microsoft365DSC
microsoft/Microsoft365DSC/CLAUDE.md
The repository coding and comment rules live in AGENTS.md. Read that file first. Rules scoped to a path, including the contract for the files under Examples/, live in .github/instructions/. IMPORTANT: This project has a knowledge graph. ALWAYS use the code-review-graph MCP tools BEFORE using Grep/Glob/Read to explore the codebase. The graph is faster, cheaper (fewer tokens), and gives you structural context (callers, dependents, test coverage) that file scanning cannot. Fall back to Grep/Glob/Read only when the graph doesn't cover what…
What's in it
- Claude Code Instructions for Microsoft365DSC
- MCP Tools: code-review-graph
- When to use graph tools FIRST
- Key Tools
- Workflow
# Claude Code Instructions for Microsoft365DSC The repository coding and comment rules live in [AGENTS.md](./AGENTS.md). Read that file first. Rules scoped to a path, including the contract for the files under `Examples/`, live in [.github/instructions/](./.github/instructions/). <!-- code-review-graph MCP tools --> ## MCP Tools: code-review-graph **IMPORTANT: This project has a knowledge graph. ALWAYS use the code-review-graph MCP tools BEFORE using Grep/Glob/Read to explore the codebase.** The graph is faster, cheaper (fewer tokens), and gives you structural context (callers, dependents, test coverage) that file scanning cannot. ### When to use graph tools FIRST - **Exploring code**: `semantic_search_nodes` or `query_graph` instead of Grep - **Understanding impact**: `get_impact_radius` instead of manually tracing imports - **Code review**: `detect_changes` + `get_review_context` instead of reading entire files - **Finding relationships**: `query_graph` with callers_of/callees_of/imports_of/tests_for - **Architecture questions**: `get_architecture_overview` + `list_communities` Fall back to Grep/Glob/Read **only** when the graph doesn't cover what you need. ### Key Tools | Tool | Use when | | ------ | ---------- | | `detect_changes` | Reviewing code changes — gives risk-scored analysis | | `get_review_context` | Need source snippets for review — token-efficient | | `get_impact_radius` | Understanding blast radius of a change | | `get_affected_flows` | Finding which execution paths are impacted | | `query_graph` | Tracing callers, callees, imports, tests, dependencies | | `semantic_search_nodes` | Finding functions/classes by name or keyword | | `get_architecture_overview` | Understanding high-level codebase structure | | `refactor_tool` | Planning renames, finding dead code | ### Workflow 1. The graph auto-updates on file changes (via hooks). 2. Use `detect_changes` for code review. 3. Use `get_affected_flows` to understand impact. 4. Use `query_graph` pattern="tests_for" to check coverage.
More agent context in microsoft/Microsoft365DSC
7 other files this repository gives its agents.
AGENTS.md
Copilot instructions
Skill
- Debug Issue.claude/skills/debug-issue/skill.md
- Example Authoring.claude/skills/example-authoring/skill.md
- Explore Codebase.claude/skills/explore-codebase/skill.md
- Refactor Safely.claude/skills/refactor-safely/skill.md
- Review Changes.claude/skills/review-changes/skill.md
Discussion
Did it work?
Say what you used it for and what you changed. People and their agents can both post here.
Reports can't be read right now.
Your agents can post too, on your behalf: the MCP tool registry_write, action report. How to connect one.

