Microsoft Agent 365 SDK is a Python software development kit for building agents that work with Microsoft 365, Teams, Copilot Studio, and Webchat. Developers use it for agent observability, notifications, runtime utilities, and development tools.
Borrowing it
Nothing to install: this file belongs to microsoft/Agent365-python. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/microsoft/Agent365-python/main/.claude/commands/resolve-review.mdgit clone --depth 1 https://github.com/microsoft/Agent365-pythonWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/microsoft/agent365-python/resolve-review)<a href="https://agentmods.dev/commands/microsoft/agent365-python/resolve-review"><img src="https://agentmods.dev/badge/commands/microsoft/agent365-python/resolve-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/microsoft/agent365-python/resolve-review"><img src="https://agentmods.dev/badge/commands/microsoft/agent365-python/resolve-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.02267 |
| Opus 5.5 | $0.00000 | $0.00907 |
| Sonnet 5.5 | $0.00000 | $0.00453 |
| Haiku 4.5 | $0.00000 | $0.00227 |
Grade A, and why
resolve-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
88% identical to resolve-review — 78 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolve Review Comments
Automatically resolve code review comments that are marked as "Agent Resolvable: Yes" from a review generated by /review-pr or /review-staged.
Usage
/resolve-review [REVIEW_FILE_PATH]
Arguments:
REVIEW_FILE_PATH(optional) - Path to the review file. If omitted, uses the most recent review file in.codereviews/.
Examples:
/resolve-review- Resolve comments from the most recent review/resolve-review .codereviews/claude-pr123-20260124_143022.md- Resolve specific review
Instructions
You are resolving agent-resolvable code review comments. This skill supports two scenarios:
- PR Reviews: Changes are made in a git worktree to avoid disrupting your current work
- Staged Reviews: Changes are made directly in the current working directory after validation
Step 1: Locate and Parse the Review File
-
If
$ARGUMENTSis provided and non-empty, use that as the review file path -
Otherwise, find the most recent review file:
ls -t .codereviews/claude-*.md | head -1On Windows, use PowerShell:
(Get-ChildItem .codereviews/claude-*.md | Sort-Object LastWriteTime -Descending | Select-Object -First 1).FullName -
Read the review file and extract:
- Review type: PR review (contains "PR Number:") or staged review (contains "Review Type: Pre-commit")
- PR number (if PR review): Extract from the metadata
- All findings marked "Agent Resolvable: Yes": Parse the structured issues
-
If no resolvable issues are found, inform the user and exit.
-
Create a todo list tracking each resolvable issue to be fixed.
Step 2: Environment Setup (Branching Strategy)
For PR Reviews (use git worktree for isolation):
Git worktree allows you to work on a different branch without changing your current working directory. This is critical to avoid disrupting the user's in-progress work.
- Get the PR's head branch name:
gh pr view <PR_NUMBER> --json headRefName --jq '.headRefName'
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 250 lines · 0 tokens per session scan A 0e08a1b5d0ab
resolve-review is a command published in the GitHub repository microsoft/Agent365-python (41 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,267 tokens. A static security scan graded it A with 0 findings. It is 88% identical to resolve-review, differing in 78 lines, and is treated as a copy.
Other commands, from other repositories
refactor
Systematic code refactoring with smart scope detection.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.