The Microsoft Agent 365 DevTools CLI is a command-line interface tool designed to streamline the development, deployment, and management of Microsoft Agent 365 applications.
Use this agent when code has been written or modified and needs to be reviewed from a high-level design and architecture perspective to ensure alignment with documented design principles. This agent should be called proactively after logical code changes are completed, before committing or merging…
Use this agent when the user has recently written, modified, or committed code and needs comprehensive code review feedback. This agent should be invoked after any significant code changes (not for the entire codebase unless explicitly requested). Examples:\n\n \nContext: User just implemented a new feature with…
Use this agent when you need expert code review for C#/.NET implementations using the Microsoft Agent 365 DevTools CLI. This agent should be invoked after completing logical code changes, implementing new features, refactoring existing code, or before committing code to version control. Examples:\n\n \nContext: The…
Use this agent to perform semantic code analysis on PR changes. Analyzes actual code logic, identifies specific issues with line references, and generates actionable feedback based on repository coding standards.
Use this agent when you need to systematically address code review comments on a pull request. This agent should be invoked when:\n\n \nContext: A pull request has been reviewed and multiple code review comments need to be addressed.\nuser: "Can you help me address the code review comments on PR #123?"\nassistant…
Use this agent when the user provides or references a Product Requirements Document (PRD) and needs it broken down into actionable development tasks. This agent should be invoked when:\n\n- The user shares a new PRD or feature specification that needs implementation planning\n- The user asks to break down requirements…
Use this agent when the user requests creation of a Product Requirements Document (PRD), asks to document a new feature, mentions writing requirements, or describes functionality that needs formal specification. This agent should be launched proactively when:\n\n \nContext: User describes a feature they want to…
Use this agent when the user asks you to implement a specific coding task, feature, or bug fix that requires writing production-quality code. This agent should be used proactively after the user provides implementation requirements or references a task from a PRD/task list.\n\nExamples:\n\n \nContext: User has a task…
Use this agent when code changes have been made and you need to verify test coverage and quality. Specifically:\n\n \nContext: User has just implemented a new command in the CLI.\nuser: "I've added a new status command that checks Azure deployment health"\nassistant: "I can see you've implemented the status command.…