菜单
File a bug report or feature suggestion on GitHub via gh CLI. Gathers details conversationally, previews, and creates an issue. Use when the user wants to report a bug or suggest a feature.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/microsoft/MCS-Agent-Builder --skill feedback命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use this skill when the user asks Claude to autonomously test, fix, review, and merge a change end-to-end. Detects which lane(s) changed (frontend / backend / framework / agentspec), spawns relevant verifiers (agentic-test-loop with --require-oracle for false-green prevention; backend-verify for contracts/types/unit/server), runs a facilitator review loop using qa-challenger via Agent tool with worktree isolation until score>=9 and zero critical findings, calls multi-model-review.js review-merged as the final pre-merge oracle, and auto-merges via gh pr merge --auto if all gates pass and the change is not on the auto-merge denylist. User notified only on auto-merge completion or escalation. Triggered by /iterate, by phrases like 'make it work', 'iterate to green', 'fix and ship', or after Claude completes any non-trivial implementation in Layer A. Does NOT fire inside /mcs-* skills (they own their build/eval/fix loop) — for that, use /mcs-iterate.
Use this skill to build an agent in Copilot Studio from a researched agentspec.json. Runs pre-build validation (auth, env, connections, tools, model), then creates the agent, configures instructions, knowledge, tools, model, topics, and publishes. Supports single-agent, multi-agent, and connected-agent architectures. Use after /mcs-research when agentspec.json is ready, or to resume a partially completed build.
Use this skill to test an agent's quality after building or fixing it. Runs eval test sets against a published agent via Direct Line API (default, auto), CopilotStudio SDK, Power CAT Kit, or MCS Native Eval (for MCP agents). Results are written per-test to evalSets[].tests[].lastResult in agentspec.json. Use after /mcs-build or /mcs-fix, or when the user wants to re-test.
基于 SOC 职业分类
正在显示 SKILL.md
| name | feedback |
| description | File a bug report or feature suggestion on GitHub via gh CLI. Gathers details conversationally, previews, and creates an issue. Use when the user wants to report a bug or suggest a feature. |
| user_invocable | true |
File bugs and suggestions on GitHub without leaving the dashboard.
From the invocation, determine the feedback type:
bug (or user describes something broken/wrong/failing) → Bugsuggest or enhancement (or user describes something they want added/improved) → SuggestionAuth & tooling check — run gh auth status. If not authenticated, tell the user to run gh auth login and stop.
Account confirmation (MANDATORY) — show the user the signed-in account from gh auth status output and ask them to confirm:
You're signed in as [username]. Issues will be created in microsoft/MCS-Agent-Builder. Is this correct?
Do NOT proceed until the user confirms. If they say no, help them switch accounts with gh auth login.
Check for pre-filled context — if args were passed (from the dashboard dialog), extract the context and skip the "ask" step. The format is: [bug|suggest] Project: X | Agent: Y | Page: Z | ... | User says: "description". Use the "User says" portion as the description and the rest as auto-context.
If no args, ask ONE question:
Auto-gather context Claude already knows:
Generate issue:
For bugs:
Bug: <concise summary> (under 70 chars)bug## What happened
[user's description]
## Steps to reproduce
[extracted from description, or "Not provided"]
## Expected behavior
[extracted or inferred]
## Environment
- Account: [if known]
- Environment: [if known]
- Skill/workflow: [if applicable]
- Page: [if provided]
For suggestions:
Suggestion: <concise summary> (under 70 chars)enhancement## Problem / motivation
[why this would help]
## Proposed solution
[what the user wants]
## Context
- Area: [dashboard, skills, build workflow, etc.]
- Related: [any related features or components]
- Page: [if provided]
Preview — show the full title + body to the user and ask:
Here's the issue I'll create. Want me to submit it, or would you like to change anything?
On confirmation — run:
gh issue create --repo microsoft/MCS-Agent-Builder --title "Bug: ..." --body "$(cat <<'EOF'
<body>
EOF
)" --label bug
(Use --label enhancement for suggestions.)
Return the issue number and URL to the user.
microsoft/MCS-Agent-Builder