chat-perf Skill
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline. Published by microsoft in vscode.
Decision snapshot
Is this a fit?
Testing, Documentation, Design and media, Includes SKILL.md
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
1 month ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is chat-perf Skill?
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline. Published by microsoft in vscode. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Documentation
- Design and media
- Testing use cases
- Documentation use cases
Declared skill metadata
- Source file: .github/skills/chat-perf/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use chat-perf Skill
- Use it for testing.
- Use it for documentation.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode
- Skill file: .github/skills/chat-perf/SKILL.md
What it does
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
Skill instructions
Chat Performance Testing When to use - Before/after modifying chat rendering code (chatListRenderer.ts, chatInputPart.ts, markdown rendering) - When changing the streaming response pipeline or SSE processing - When modifying disposable/lifecycle patterns in chat components - To compare performance between two VS Code releases - In CI to gate PRs that touch chat UI code Quick start bash Run perf regression test (compares local dev build vs VS Code 1.115.0): npm run perf:chat -- --scenario text-only --runs 3 Run all scenarios with no baseline (just measure): npm run perf:chat -- --no-baseline --runs 3 Compare two local builds (apples-to-apples): npm run perf:chat -- --build /path/to/build-A --baseline-build /path/to/build-B --runs 5 Build a local production package and compare against a release: npm run perf:chat -- --production-build --baseline-build 1.115.0 --runs 5 Run memory leak check (10 messages in one session): npm run perf:chat-leak Run leak check with more messages for accuracy
Verified compatibility and discovery
Frequently asked questions
What is chat-perf?
chat-perf is a open-source AI agent skill with Copy skill directory. Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version.
Who is chat-perf best for?
chat-perf is best for reusing agent instructions, scripts, and references, testing workflows, documentation workflows, design and media workflows.
How do I install chat-perf?
Install or run chat-perf using Copy skill directory. Check chat-perf for the latest setup command.
Is chat-perf actively maintained?
chat-perf may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
