golden-artifact-testing
Use when designing or repairing golden-file, snapshot, fixture, or generated-artifact tests. Triggers:
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 11-02 00:09
13,035 results
Use when designing or repairing golden-file, snapshot, fixture, or generated-artifact tests. Triggers:
Use when auditing install, setup, bootstrap, or update scripts for safe, idempotent behavior. Triggers:
Use when building real-service end-to-end tests with fixtures, cleanup, rate limits, and evidence. Triggers:
Use when designing metamorphic tests for oracle-poor behavior using invariants and input relations. Triggers:
Use when coordinating browser or UI tests through NTM panes with screenshots and handoffs. Triggers:
Use when preparing releases with versioning, changelog, artifacts, smoke tests, tags, and go/no-go. Triggers:
Python testing framework for writing simple, scalable, and powerful tests
Guide for using pytest-mock plugin to write tests with mocking. Use when writing pytest tests that need mocking, patching, spying, or stubbing. Covers mocker…
Work with pytest-recording (VCR.py) for recording and replaying HTTP interactions in tests. Use when writing VCR tests, managing cassettes, configuring VCR…
Fetch a GitHub PR diff with old/new line numbers and auto-generated-file masking for code review. Use when you need a pull request's diff annotated with line…
Run wshobson PluginEval over this repo's skills and write a `# PluginEval Report` to an `EVALS.md` in each skill's folder. Use when the user wants to evaluate,…
This skill should be used when anything breaks or behaves unexpectedly and before proposing any fix. It applies to bug reports, failing or flaky tests, build failures, crashes, regressions, performance degradation, and pasted stack traces or error logs. It also applies when the user says "debug this", "fix this bug", "why is this failing", "it worked before", or "something is broken". It should not be used for building new features (use follow-tdd) or for troubleshooting Claude Code itself (use the bundled /debug).
Use ONLY when writing, porting, reviewing, debugging, or running application code for Moore Threads MUSA or MTT S5000, especially CUDA-to-MUSA migration,…
Debug an issue by identifying root causes, fixing the most probable one, testing, and committing. Use with "/dev-debug <description of the issue>".
Test the BrowserOS app extension UI by starting the dev environment and visually verifying changes via CDP. Covers the new tab page (left sidebar — Home,…
Use when selecting, implementing, or stress-testing the causal identification strategy for an empirical economics manuscript — difference-in-differences…
Build and verify replication packages — routes to reproducibility-auditor agent
This skill covers structural econometric models. Use when the user is building, estimating, or debugging structural models — including BLP demand estimation,…
Prose quality checker for Quarto (.qmd) files, grounded in William Zinsser's *On Writing Well* (30th Anniversary Edition). Checks for clutter, weak verbs,…
Use when anticipating how an expert Annals of Mathematics referee will verify a proof — stress-testing the argument for gaps, checking external dependencies,…
Use when judging whether a psychology topic is mature, important, and synthesis-ready enough to warrant an Annual Review of Psychology (ARPsych) review. Tests…
Use when choosing or sharpening a research question for a Journal of International Business Studies (JIBS) manuscript — testing whether it is a genuine…
Use when the research question or contribution is the bottleneck for a The Review of Financial Studies (RFS) manuscript. Pressure-tests novelty-plus-rigor fit…
Use when an empirical analysis should be RUN and audited, not just advised — DiD, IV, RDD, synthetic control, DML, multiple-testing, sensitivity. Maps the…