test-review

name	test-review
description	Review the current conversation against a /troubleshoot test case's expected response, then generate an issue report. Use when user says "review test", "check results", "grade test", "compare expected", or wants to file an issue for a test case.

Test Review

Compares the /troubleshoot response in the current conversation against the expected criteria from a test case file, then generates a ready-to-file issue report.

Workflow

1. Identify the test case

Ask the user which test number to review, or infer it from context (e.g., the test case file open in the editor, or the /troubleshoot query that was run).

2. Read the test case file

Read test-cases/test-<NN>.md to get:

• The title (first # heading)
• The Expected response should include checklist (the - [ ] items)
• The Create Issue URL at the bottom

3. Evaluate each criterion

Look at the /troubleshoot response earlier in the conversation. For each expected criterion, determine:

• Pass — the response clearly addresses this point
• Fail — the response does not address or contradicts this point

Be honest and objective. A criterion passes only if the response substantively covers it (not just tangentially mentions it).

4. Output a results summary

Display a table like:

#	Criterion	Result
1	Identifies X	Pass
2	Names Y	Fail
...	...	...

5. Generate the issue body

Build a markdown block the user can copy-paste as a GitHub issue body. Format:

## Test Case: test-<NN> — <title>

**Result:** X/Y criteria passed

| # | Criterion | Result |
|---|-----------|--------|
| 1 | ... | ... |

### Notes
<any additional observations about the response quality>

6. Show the Create Issue link

After showing the results, display the Create Issue URL from the test case as a clickable markdown link so the user can open it directly from chat:

[Create Issue](https://github.com/microsoft/vscode/issues/new?template=blank&body=Testing+%23301037%0A%0A&assignees=pwang347)