Menü
Review whether Burrete changes have the right focused validation.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Preview supported molecular attachments or an explicit public PDB ID in Burrete's interactive viewer, or use the bounded hosted Ketcher editor for transient chemical sketches.
Use when an external agent must open, observe, control, or render into a Burrete molecular workspace without managing transport details.
Primary router for Burrete. Use when the plugin is at-mentioned or for molecular workspace work: opening structures, operating Mol* or Ketcher, reviewing SDF/property collections, trajectories, workflow result bundles, molecular reports, or Browser/Computer visual QA.
Use when opening molecular artifacts in Burrete Browser preview or desktop app sessions and establishing an observable workspace.
Use when visually verifying Burrete Browser preview or desktop app state without replacing typed observe/action contracts.
Use when molecular notes, property tables, charts, workflow reports, or provenance should be rendered beside an active Burrete workspace.
| name | burrete-review-testing |
| description | Review whether Burrete changes have the right focused validation. |
Use this skill when reviewing whether a change is adequately verified.
samples/ or
tests/fixtures/.Use docs/tools/index.md and docs/tools/testing-surfaces.md to pick the
narrowest relevant command. Common checks include:
bun tests/test-ui-shell-contract.mjs
bun tests/test-viewer-bridge-message-contract.mjs
bun tests/test-runtime-storage-contract.mjs
bun tests/test-dev-namespace.mjs
bun tests/test-quicklook-preview-smoke-contract.mjs
bun tests/test-agent-preview-server.mjs
bun run test:agent
bun run test:update
bun run test:ui
bun run test:tauri-structure
bun run check
vp check
vp test
For packaged desktop or Finder Quick Look changes, browser checks are not
enough. Require the documented build/install/smoke flow with a unique
BURRETE_DEV_FLAVOR unless the user explicitly scoped the task away from native
verification.
List missing tests or mismatched validation with the changed behavior they fail to cover.