microsoft / microsoft/Power-CAT-Copilot-Studio-Kit

Bug: Agent Review Tool - Review rules can be applied to the wrong topic or component (Standard Harness)

Open
#873 0 comments 0 reactions 1 assignee View on GitHub

@Ramakrishnan24689 is already working on this.

Since Sep 18, 2026.

bug
Dominant language
TypeScript
Stars
450
Forks
95
Avg merge
26m
Merged PRs (30d)
5

Description

Description

The Agent Review Tool can apply a rule without considering how a topic starts or what type of component it reviews.

Example

A test agent contains an event-triggered topic called Daily sync, a redirect topic called Send to specialist, a phrase-triggered topic called Help, and a connected agent called Product Helper. It also has an input called Request number with an existing description. The review reports routing findings for the event and redirect topics, identifies Product Helper as a general tool, and reports the input description as missing.

Steps to reproduce
  1. Create a test agent with the components described above.

  2. Add instructions that cover escalation but not cancellation.

  3. Run an agent review.

  4. Inspect the topic, component, input, and instruction findings.

Expected behavior

Evaluate Daily sync as an event topic and Help as a phrase-triggered topic. Do not apply direct user-routing rules to Send to specialist. Identify Product Helper as a connected agent. Recognize the existing Request number description. Report the instructions as incomplete, not fully missing. Show information that cannot be confirmed as Not assessed.

Actual behavior

In the reviewed version, some rules were applied without enough topic or component context. Existing information could be reported as missing, and an uncertain result could be shown as a definite finding.

Environment

No response

Additional context or logs

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.