Stryker Js
Introduce StrykerJS mutation testing or assess JavaScript/TypeScript test quality. Use Git diff mutations in CI and surviving mutants locally to find missing cases and weak assertions, including tests generated by AI.
Install
npx skills add mizchi/skills --skill stryker-jsgit clone --depth 1 https://github.com/mizchi/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/stryker-js ~/.claude/skills/stryker-jsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# StrykerJS: measure test quality Use mutation testing to ask whether tests detect plausible defects in production code. A passing suite or high coverage alone does not answer that question. Mutate production source; improve the tests that fail to detect meaningful mutations. Upstream package baseline (2026-11-16): `@stryker-mutator/core@10.1.1` requires Node `>=22.0.0`; maintained examples here use Node 24+. A newer upstream version triggers review, not automatic replacement of a consumer's compatible pinned runner cohort. ## Choose the work - **Introduce Stryker:** read [setup.md](references/setup.md), adapt the assets, and verify the integration with a small real module before widening the scope. - **Review or improve tests locally:** read [evaluate-tests.md](references/evaluate-tests.md). Run mutations, inspect the surviving changes and covering tests, then improve the missing inputs or assertions. - **Add CI:** copy [mutation-diff.yml](assets/mutation-diff.yml) to `.github/workflows/mutation-diff.yml`, along with the selector scripts and package commands. CI must pass `--diff-only`. Retain the project's runner, configuration, workspace layout and package manager. The supplied integration targets pnpm, Node.js 24+ and Vitest; use the appropriate Stryker runner for Jest/Mocha rather than migrating tests just to use these snippets. Match `@stryker-mutator/core` and runner versions and check their actual peer dependencies. ## CI and local scope
Details
- Skill name
stryker-js- Repository
- mizchi/skills
- Path
stryker-js/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Stryker Js skill do?
Introduce StrykerJS mutation testing or assess JavaScript/TypeScript test quality. Use Git diff mutations in CI and surviving mutants locally to find missing cases and weak assertions, including tests generated by AI.
How do I install the Stryker Js skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add mizchi/skills --skill stryker-js. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Stryker Js popular?
It lives in mizchi/skills, which has 423 GitHub stars and 6 forks.
Related skills
Actions CI Tuning
423mizchi/skills
Use when auditing or improving GitHub Actions workflows for a project. Covers cache setup (npm/pnpm/yarn), job parallelism, shard-based test splitting, artifact handling pitfalls, and Playwright-specific patterns. Trigger on: slow CI, cache miss, flaky shard jobs, merge-reports failures, or an explicit 'tune CI' request.
AI Index
423mizchi/skills
Method and tooling for measuring how AI-generated a piece of prose reads, in Japanese or English. Two layers — a deterministic lint for removable surface tells (scripts/slopscore.py, no API) and a judgment layer of typed probabilistic questions (Jev noul/score) for the tells that survive editing. Includes measured human/AI baselines, a gap-first calibration procedure, and labeled fixtures. Use when building or calibrating an AI-likeness score, or when a draft needs a defensible number rather than a vibe. For writing guidance use natural-writing-ja / natural-writing-en instead.
Apm Usage
423mizchi/skills
Reference for APM manifests, installation, targeted updates, deployment paths and lockfiles. Invoke when the user explicitly asks about APM or apm.yml, or an unfamiliar APM command/error needs exact CLI details. Do not automatically invoke for every project that happens to have installed skills.
Tech Trend Watch
423mizchi/skills
Long-term technology stack review using State of JS, State of CSS, and Thoughtworks Technology Radar — satisfaction×usage matrix, ADOPT/TRIAL/ASSESS/HOLD mapping, P0–P3 migration priority. Use for annual stack audits, planning major migrations (jest→vitest, webpack→Vite, etc.), or on-demand replacement decisions. Not for general architecture design.
Playwright Test
423mizchi/skills
Best practices and reference for Playwright Test (E2E). Covers how to write tests, avoiding fixed waits, network triggers, DnD, shard/retry setup on GitHub Actions, and more. Use when writing, reviewing, or configuring CI for Playwright tests.
Multica Artifact Architect
279it235/multica-best-practices
Land technical design artifacts to the code repo or knowledge platform (default Git repo / Confluence). Used by @Architect to upload technical design for downstream implementation and test consumption. Swappable platform.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.