Content
75%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A highly actionable, well-structured reference for the VS Code integration test scripts: all commands are executable and the prerequisite (compilation) is called out. The main weakness is redundancy — the Examples section duplicates commands already shown under Options and CI job details add density — and no separate reference files are used for the more peripheral detail.
Suggestions
Trim the "## Examples" section to only novel combinations (e.g. --run + --grep) and drop examples that already appear verbatim under the Options sections, cutting roughly 20 lines of duplication.
Condense the GitHub/ADO CI job-name details into one or two sentences or move them into a separate reference file, keeping only the actionable fact that Agent Host E2E suites are not run by these scripts.
Consider collapsing "## Options" per-option bash blocks that repeat identical commands (e.g. the --run example appears in both Options and Examples) into a single canonical set of invocations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The "## Examples" section largely re-prints commands already shown under Options ("--run src/vs/workbench/services/search/test/browser/search.integrationTest.ts", "--grep \"TextSearchProvider\"", and "--suite git" each appear twice), and the Agent Host E2E paragraph packs GitHub/ADO CI job names into one dense sentence. The body is otherwise repo-specific with no general-concept padding, so it is not the noticeable verbosity of a 2, but it could clearly be tightened. | 3 / 5 |
Actionability | Every command is copy-paste ready with real paths, globs, and quoting — e.g. "./scripts/test-integration.sh --runGlob \"**/search/**/*.integrationTest.js\"" and "./scripts/test-integration.sh --suite api-folder --grep 'should open'" — and the examples cover all the common cases (run all, single file, grep, glob, suite, combinations). | 5 / 5 |
Workflow Clarity | A prerequisite checkpoint is explicit ("Ensure the `VS Code - Build` watch task is running or that compilation has completed before running tests") and the "Distinction from unit tests" section prevents the most likely wrong-tool mistake. There is no validate/fix/retry loop, but running tests is neither destructive nor a batch operation, so the feedback-loop cap does not apply; it falls short of a 5 because the overall flow is a reference layout rather than an explicitly sequenced process. | 4 / 5 |
Progressive Disclosure | The body is well organized into per-option sections with concrete headers and an external pointer ("See src/vs/platform/agentHost/test/node/e2e/README.md") at one level deep, and no bundle files exist so a single self-contained file is appropriate. The CI job-name details (GitHub and ADO job/step names) are arguably inlinable reference material that could move to a separate file, which keeps it at a 4 rather than a 5. | 4 / 5 |
Total | 16 / 20 Passed |