Verwenden Sie diese Fähigkeit, um einen UI-Fehler zu reproduzieren oder eine Korrektur zu überprüfen, indem Sie ein echtes VS Code-Fenster End-to-End steuern und Beweise erfassen. Sie schreibt eine Szenariodatei, führt sie gegen einen Dev-Build oder installierte Insiders aus und erstellt ein beschriftetes Video, Screenshots pro Schritt, einen Playwright-Trace und einen HTML-Bericht, der an ein Issue oder einen Pull Request angehängt werden kann.
Diese Fähigkeit ermöglicht es, UI-Fehler in VS Code zu reproduzieren oder Korrekturen End-to-End zu verifizieren. Sie steuert ein echtes VS Code-Fenster, führt eine benutzerdefinierte Szenariodatei aus und erstellt umfassende Beweise wie beschriftete Videos, Screenshots pro Schritt, Playwright-Traces und HTML-Berichte. Dies ist besonders nützlich für Entwickler, die Fehlerberichte mit visuellen und technischen Details untermauern möchten, um sie an Issues oder Pull Requests anzuhängen. Die Fähigkeit unterstützt Dev-Builds und installierte Insiders-Versionen von VS Code und nutzt moderne Testwerkzeuge wie Playwright für die Automatisierung.
npx skills add microsoft/vscodeVerwenden Sie diese Fähigkeit, um einen UI-Fehler zu reproduzieren oder eine Korrektur zu überprüfen, indem Sie ein echtes VS Code-Fenster End-to-End steuern und Beweise erfassen. Sie schreibt eine Szenariodatei, führt sie gegen einen Dev-Build oder installierte Insiders aus und erstellt ein beschriftetes Video, Screenshots pro Schritt, einen Playwright-Trace und einen HTML-Bericht, der an ein Issue oder einen Pull Request angehängt werden kann.
This repo contains 11 individual skills — each has its own dedicated page.
Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI. Covers accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles.
Agents workbench layout — covers the fixed layout structure, grid configuration, part visibility, editor modal, titlebar, sidebar footer, and implementation requirements. Use when implementing features or fixing issues in the Agents workbench layout.
Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.
Use when validating Azure DevOps pipeline changes for the VS Code build. Covers queueing builds, checking build status, viewing logs, and iterating on pipeline YAML changes without waiting for full CI runs.
Guidelines for fixing unhandled errors from the VS Code error telemetry dashboard. Use when investigating error-telemetry issues with stack traces, error messages, and hit/user counts. Covers tracing data flow through call stacks, identifying producers of invalid data vs. consumers that crash, enriching error messages for telemetry diagnosis, and avoiding common anti-patterns like silently swallowing errors.
Use when making code changes to ensure they pass VS Code's hygiene checks. Covers the pre-commit hook, unicode restrictions, string quoting rules, copyright headers, indentation, formatting, ESLint, and stylelint. Run the hygiene check before declaring work complete.
Audit code for memory leaks and disposable issues. Use when reviewing event listeners, DOM handlers, lifecycle callbacks, or fixing leak reports. Covers addDisposableListener, Event.once, MutableDisposable, DisposableStore, and onWillDispose patterns.
Agents window architecture — covers the agents-first app, layering, folder structure, chat widget, menus, contributions, entry points, and development guidelines. Use when implementing features or fixing issues in the Agents window.
Ensure renamed built-in tool references preserve backward compatibility. Use when renaming a toolReferenceName, tool set referenceName, or any tool identifier. Run on ANY change to tool registration code. Covers legacyToolReferenceFullNames for tools and legacyFullNames for tool sets.
Download screenshot baselines from the latest CI run and commit them. Use when asked to update, accept, or refresh component screenshot baselines from CI, or after the screenshot-test GitHub Action reports differences. This skill should be run as a subagent.
Use when reproducing a UI bug or verifying a fix by driving a real VS Code window end to end and capturing evidence. Writes a scenario file, runs it against a dev build or installed Insiders, and produces a captioned video, per-step screenshots, a Playwright trace, and an HTML report to attach to an issue or pull request.
Extract frames or short clips from videos using ffmpeg.
Summarize or transcribe URLs, YouTube/videos, podcasts, articles, transcripts, PDFs, and local files.
Use when testing, fixing, or extending the OpenClaw Control UI GUI with Vitest + Playwright end-to-end checks, mocked Gateway WebSocket flows, mocked dashboard runs, screenshots/videos, or agent-verifiable browser proof.
Obra superpowers agent skills.
See, Understand, Act on video and audio. See- ingest from local files, URLs, RTSP/live feeds, or live record desktop; return realtime context and playable stream links. Understand- extract frames, build visual/semantic/temporal indexes, and search moments with timestamps and auto-clips. Act- transcode and normalize (codec, fps, resolution, aspect ratio), perform timeline edits (subtitles, text/image overlays, branding, audio overlays, dubbing, translation), generate media assets (image, audio...
End-to-end marketing campaign planning and execution. Covers audience research, positioning, campaign angle definition, landing page copy, email sequences, social posts, ad copy, short-form video scripts, and content calendars. Use as the orchestration layer for multi-channel product launches. Use when planning or executing a multi-channel product launch, or producing landing page, email, social, or ad copy.