code-ai-installer 3.0.0 → 4.0.1-a

package/domains/development/locales/en/.agents/skills/mongodb-mongoose-best-practices-reference/agents/gemini.json

@@ -0,0 +1,19 @@
+{
+  "name": "mongodb-mongoose-best-practices-reference",
+  "display_name": "MongoDB + Mongoose Code Reference (DO/DON'T)",
+  "description": "Canonical MongoDB and Mongoose code reference — detailed DO/DON'T examples across 10 topics — schema design, Mongoose setup, indexes, query patterns, connection, transactions, migrations, error handling, testing, anti-patterns. Activate when looking up a specific code pattern.",
+  "default_prompt": "Use $mongodb-mongoose-best-practices-reference when the task matches the \"MongoDB + Mongoose Code Reference (DO/DON'T)\" skill.",
+  "triggers": [
+    "mongodb-mongoose-best-practices-reference",
+    "mongodb mongoose best practices reference",
+    "MongoDB + Mongoose Code Reference (DO/DON'T)",
+    "Canonical MongoDB and Mongoose code reference — detailed DO/DON'T examples across schema design, Mongoose setup, indexes, query patterns, connection, transactions, migrations, error handling, testing, anti-patterns"
+  ],
+  "capabilities": [
+    "mongodb",
+    "mongoose",
+    "reference"
+  ],
+  "tools": [],
+  "implicit_invocation": true
+}

package/domains/development/locales/en/.agents/skills/mongodb-mongoose-best-practices-reference/agents/kimi.yaml

@@ -0,0 +1,15 @@
+name: "mongodb-mongoose-best-practices-reference"
+display_name: "MongoDB + Mongoose Code Reference (DO/DON'T)"
+description: "Canonical MongoDB and Mongoose code reference — detailed DO/DON'T examples across 10 topics — schema design, Mongoose setup, indexes, query patterns, connection, transactions, migrations, error handling, testing, anti-patterns. Activate when looking up a specific code pattern."
+default_prompt: "Use $mongodb-mongoose-best-practices-reference when the task matches the \"MongoDB + Mongoose Code Reference (DO/DON'T)\" skill."
+triggers:
+  - "mongodb-mongoose-best-practices-reference"
+  - "mongodb mongoose best practices reference"
+  - "MongoDB + Mongoose Code Reference (DO/DON'T)"
+  - "Canonical MongoDB and Mongoose code reference — detailed DO/DON'T examples across schema design, Mongoose setup, indexes, query patterns, connection, transactions, migrations, error handling, testing, anti-patterns"
+capabilities:
+  - "mongodb"
+  - "mongoose"
+  - "reference"
+tools: []
+implicit_invocation: true

package/domains/development/locales/en/.agents/skills/mongodb-mongoose-best-practices-reference/agents/openai.yaml

@@ -0,0 +1,8 @@
+interface:
+  display_name: "MongoDB + Mongoose Code Reference (DO/DON'T)"
+  short_description: "Canonical MongoDB and Mongoose code reference — detailed DO/DON'T examples across 10 topics — schema design, Mongoose setup, indexes, query patterns, connection, transactions, migrations, error handling, testing, anti-patterns. Activate when looking up a specific code pattern."
+  default_prompt: "Use $mongodb-mongoose-best-practices-reference when the task matches the \"MongoDB + Mongoose Code Reference (DO/DON'T)\" skill."
+dependencies:
+  tools: []
+policy:
+  allow_implicit_invocation: true

package/domains/development/locales/en/.agents/skills/mongodb-mongoose-best-practices-reference/agents/qwen.json

@@ -0,0 +1,19 @@
+{
+  "name": "mongodb-mongoose-best-practices-reference",
+  "display_name": "MongoDB + Mongoose Code Reference (DO/DON'T)",
+  "description": "Canonical MongoDB and Mongoose code reference — detailed DO/DON'T examples across 10 topics — schema design, Mongoose setup, indexes, query patterns, connection, transactions, migrations, error handling, testing, anti-patterns. Activate when looking up a specific code pattern.",
+  "default_prompt": "Use $mongodb-mongoose-best-practices-reference when the task matches the \"MongoDB + Mongoose Code Reference (DO/DON'T)\" skill.",
+  "triggers": [
+    "mongodb-mongoose-best-practices-reference",
+    "mongodb mongoose best practices reference",
+    "MongoDB + Mongoose Code Reference (DO/DON'T)",
+    "Canonical MongoDB and Mongoose code reference — detailed DO/DON'T examples across schema design, Mongoose setup, indexes, query patterns, connection, transactions, migrations, error handling, testing, anti-patterns"
+  ],
+  "capabilities": [
+    "mongodb",
+    "mongoose",
+    "reference"
+  ],
+  "tools": [],
+  "implicit_invocation": true
+}

package/domains/development/locales/en/.agents/skills/mongodb-mongoose-best-practices-reference/agents/skill.yaml

@@ -0,0 +1,23 @@
+version: 1
+name: "mongodb-mongoose-best-practices-reference"
+display_name: "MongoDB + Mongoose Code Reference (DO/DON'T)"
+description: "Canonical MongoDB and Mongoose code reference — detailed DO/DON'T examples across 10 topics — schema design, Mongoose setup, indexes, query patterns, connection, transactions, migrations, error handling, testing, anti-patterns. Activate when looking up a specific code pattern."
+default_prompt: "Use $mongodb-mongoose-best-practices-reference when the task matches the \"MongoDB + Mongoose Code Reference (DO/DON'T)\" skill."
+triggers:
+  - "mongodb-mongoose-best-practices-reference"
+  - "mongodb mongoose best practices reference"
+  - "MongoDB + Mongoose Code Reference (DO/DON'T)"
+  - "Canonical MongoDB and Mongoose code reference — detailed DO/DON'T examples across schema design, Mongoose setup, indexes, query patterns, connection, transactions, migrations, error handling, testing, anti-patterns"
+capabilities:
+  - "mongodb"
+  - "mongoose"
+  - "reference"
+tools: []
+invocation:
+  explicit: true
+  implicit: true
+localization:
+  default_locale: "en"
+  available_locales:
+    - "ru"
+    - "en"

package/domains/development/locales/en/.agents/skills/mutation-testing-setup/SKILL.md

@@ -0,0 +1,335 @@
+---
+name: mutation-testing-setup
+description: "Production-grade wiring for mutation testing on CI/CD — Stryker (JS/TS) + mutmut (Python) with matrix parallel, PR incremental + nightly full run on cron, gh check Required status binding, tier-aware threshold gates (80%/60%/optional from $testing-strategy-js §7), Stryker dashboard secret management, output format for $test-integrity-hooks-setup §4 aggregator. Production complement to the minimal-CI workflow from $qa-mutation-testing §6. Activate at production repo bootstrap, when scaling minimal-CI to matrix, when adding nightly full run, when connecting to the test-integrity aggregator."
+type: discretionary
+domain: development
+owners:
+  - devops
+  - tester
+gates:
+  - OPS
+  - TEST
+tech:
+  - stryker
+  - mutmut
+topic:
+  - qa
+  - ops
+  - testing
+triggers:
+  - mutation testing setup
+  - stryker production config
+  - mutmut production config
+  - mutation CI matrix
+  - mutation nightly run
+  - stryker dashboard token
+  - .stryker.conf.mjs
+  - mutmut.toml
+  - mutation testing CI setup
+  - production mutation testing
+related:
+  - qa-mutation-testing
+  - qa-regression-baseline
+  - qa-flaky-test-protocol
+  - qa-property-based-testing
+  - qa-test-integrity-audit
+  - testing-strategy-js
+  - testing-strategy-js-reference
+  - tdd-workflow
+  - tdd-workflow-reference
+  - tests-quality-review
+  - tests-integrity-rules
+  - test-integrity-hooks-setup
+  - deployment-ci-plan
+  - deployment-ci-plan-reference
+budget_lines: 360
+schema_version: 1
+---
+
+
+# Skill: Mutation Testing Setup (DevOps + Tester)
+
+Production-grade wiring for mutation testing on CI/CD. `$qa-mutation-testing` provides methodology + minimal-CI on PR incremental; this skill is the production complement: matrix parallel JS+Python, nightly full run on cron, gh check binding, tier-aware threshold gates, secret management for Stryker dashboard, output format for the unified aggregator from `$test-integrity-hooks-setup §4`.
+
+**Sections:**
+1. [When to apply](#1-when)
+2. [Stryker production config](#2-stryker)
+3. [mutmut production config](#3-mutmut)
+4. [CI matrix workflow](#4-ci-matrix)
+5. [Aggregator integration](#5-aggregator)
+6. [Secret management](#6-secrets)
+7. [DoD](#7-dod)
+
+---
+
+## 1. When to apply
+
+- **Production repo bootstrap** — DevOps at OPS gate. Stryker + mutmut configs + matrix workflow + secrets + integration into `$test-integrity-hooks-setup §4`.
+- **Scaling minimal-CI → matrix** — after the first weeks of working with PR incremental from `$qa-mutation-testing §6` add parallel JS+Python jobs.
+- **Adding nightly full run** — incremental on PR does not cover unchanged tier 1-2 modules; cron nightly gives baseline drift detection.
+- **Connecting to the aggregator** — after shipping `$test-integrity-hooks-setup` you need to unify the output format for the PR comment.
+
+Prerequisite: `$qa-flaky-test-protocol` applied to flaky tests before enabling mutation gating — otherwise survived mutants will be false positives.
+
+---
+
+## 2. Stryker production config
+
+The minimal config from `$qa-mutation-testing §2` is sufficient for PR incremental. Production adds: tier-aware mutator selection, dashboard reporter, full-mode for nightly.
+
+File `.stryker.conf.mjs`:
+```js
+import path from 'node:path';
+
+const isFullRun = process.env.STRYKER_MODE === 'full';
+const tier1Paths = [
+  'src/auth/**', 'src/billing/**', 'src/security/**',
+  'src/payments/**', 'src/crypto/**',
+];
+
+export default {
+  packageManager: 'npm',
+  testRunner: 'vitest',
+  mutate: isFullRun
+    ? ['src/**/*.{ts,tsx,js}', '!src/**/*.{test,spec}.{ts,tsx,js}']
+    : tier1Paths.map(p => `${p}/*.{ts,tsx,js}`),
+  reporters: ['html', 'json', 'progress', 'dashboard'],
+  jsonReporter: { fileName: 'reports/mutation/stryker-report.json' },
+  thresholds: { high: 80, low: 60, break: 60 },
+  incremental: !isFullRun,
+  incrementalFile: '.stryker-tmp/incremental.json',
+  dashboard: {
+    project: process.env.STRYKER_DASHBOARD_PROJECT,
+    version: process.env.GITHUB_REF_NAME || 'main',
+    module: 'js',
+  },
+  timeoutMS: 60000,
+  concurrency: isFullRun ? 4 : 2,
+};
+```
+
+Tier mapping for thresholds inline:
+- `break: 60` — workflow fails if overall score < 60 (any tier; conductor.md §2 patterns go to tier 1)
+- Per-file granular threshold checked in aggregator (§5) — Stryker itself does not distinguish per-file tier
+
+Dashboard token — secret (§6).
+
+---
+
+## 3. mutmut production config
+
+The minimal config from `$qa-mutation-testing §3` is sufficient for PR incremental. Production adds: tier-aware cache scoping + matrix support.
+
+File `mutmut.toml`:
+```toml
+[tool.mutmut]
+paths_to_mutate = "src/"
+paths_to_exclude = "src/**/test_*.py"
+runner = "pytest tests/ -x --timeout=30"
+backup = false
+
+[tool.mutmut.tier_1]
+# Pre-filter in CI matrix Python job via --paths-to-mutate override:
+# auth, billing, security, payments, crypto subfolders
+priority_paths = [
+  "src/auth/",
+  "src/billing/",
+  "src/security/",
+  "src/payments/",
+  "src/crypto/",
+]
+threshold_pct = 80
+
+[tool.mutmut.tier_2]
+threshold_pct = 60
+```
+
+mutmut does not have native `dashboard`/`incremental` parameters at Stryker level. Incremental is emulated via cache restore in CI (§4). Full run overrides `paths_to_mutate` to the entire `src/`.
+
+Output: `.mutmut-cache` → converted to `mutmut-report.json` in a post-step:
+```bash
+mutmut results --json > reports/mutation/mutmut-report.json
+```
+
+---
+
+## 4. CI matrix workflow
+
+File `.github/workflows/mutation-testing.yml`:
+```yaml
+name: Mutation Testing
+
+on:
+  pull_request:
+    paths:
+      - 'src/**'
+      - 'tests/**'
+  schedule:
+    - cron: '0 2 * * *'  # nightly 02:00 UTC
+
+jobs:
+  stryker:
+    runs-on: ubuntu-latest
+    if: contains(fromJSON('["pull_request", "schedule"]'), github.event_name)
+    env:
+      STRYKER_MODE: ${{ github.event_name == 'schedule' && 'full' || 'incremental' }}
+      STRYKER_DASHBOARD_API_KEY: ${{ secrets.STRYKER_DASHBOARD_API_KEY }}
+      STRYKER_DASHBOARD_PROJECT: ${{ vars.STRYKER_DASHBOARD_PROJECT }}
+    steps:
+      - uses: actions/checkout@v4
+        with: { fetch-depth: 0 }
+      - uses: actions/setup-node@v4
+        with: { node-version: '20', cache: 'npm' }
+      - run: npm ci
+      - name: Restore incremental
+        if: env.STRYKER_MODE == 'incremental'
+        uses: actions/cache@v4
+        with:
+          path: .stryker-tmp/
+          key: stryker-incremental-${{ github.base_ref }}
+      - run: npx stryker run
+      - name: Compare to baseline
+        run: node scripts/mutation-baseline-check.mjs js
+      - uses: actions/upload-artifact@v4
+        if: always()
+        with:
+          name: stryker-report
+          path: reports/mutation/stryker-report.json
+          retention-days: 30
+
+  mutmut:
+    runs-on: ubuntu-latest
+    if: hashFiles('src/**/*.py') != ''
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: '3.12', cache: 'pip' }
+      - run: pip install -r requirements.txt mutmut
+      - name: Restore mutmut cache
+        uses: actions/cache@v4
+        with:
+          path: .mutmut-cache
+          key: mutmut-${{ github.base_ref }}
+      - run: mutmut run --paths-to-mutate=$(node scripts/mutmut-tier-paths.mjs)
+      - run: mutmut results --json > reports/mutation/mutmut-report.json
+      - name: Compare to baseline
+        run: python scripts/mutation_baseline_check.py
+      - uses: actions/upload-artifact@v4
+        if: always()
+        with:
+          name: mutmut-report
+          path: reports/mutation/mutmut-report.json
+          retention-days: 30
+```
+
+In Settings → Branches → main → Required status checks: add `Mutation Testing / stryker` (Python check added conditionally via if-hashFiles).
+
+PR incremental: ~5-15 min on a medium repo. Nightly full: 30-90 min.
+
+---
+
+## 5. Aggregator integration
+
+`$test-integrity-hooks-setup §4` aggregator expects `stryker-report.json` + `mutmut-report.json` in the `reports/mutation/` directory. This skill guarantees the output format.
+
+### Stryker → aggregator mapping
+
+Native Stryker JSON contains `files: { [path]: { mutationScore, mutants: [{ status, location, mutatorName }] } }`. The aggregator parses and applies tier-aware severity:
+
+| Condition | Severity | Source |
+|-----------|----------|--------|
+| Tier 1 file score < 80% | P0 (block-merge) | `conductor.md § 3` |
+| Tier 2 file score < 60% | P0 (block-merge) | `conductor.md § 3` |
+| Survived mutant in tier 1-2 not marked equivalent | P1 (REV-xx) | `$qa-mutation-testing §5` triage |
+| Tier 3 score regression > 5pp | P1 (REV-xx) | aggregator default |
+
+### mutmut → aggregator mapping
+
+mutmut `results --json` has a different shape: `{ killed, survived, suspicious, untested }`. Convert script:
+```bash
+node scripts/normalize-mutmut-to-aggregator.mjs \
+  < reports/mutation/mutmut-report.json \
+  > reports/mutation/mutmut-aggregator.json
+```
+
+The normaliser maps mutmut survivors to the same severity rules via mutmut paths metadata + tier detection from `conductor.md § 2`.
+
+### Baseline drift integration
+
+Score baseline is stored in `.mutation-baseline.json` (format from `$qa-mutation-testing §7`). The aggregator compares current scores vs baseline:
+- Tier 1 delta < -2pp → P0
+- Tier 2 delta < -3pp → P0
+- Tier 3 delta < -5pp → P1
+
+Baseline update is a separate PR with justification from the Tester (see `$qa-regression-baseline §7` for the TID baseline update procedure).
+
+---
+
+## 6. Secret management
+
+The Stryker dashboard token and private registry creds are mandatory for production. Do not commit them to the repo.
+
+### GitHub Secrets (per-repo)
+
+| Secret | Purpose | Source | Rotation |
+|--------|---------|--------|----------|
+| `STRYKER_DASHBOARD_API_KEY` | Auth for dashboard.stryker-mutator.io | https://dashboard.stryker-mutator.io → project settings | 6 mo |
+| `NPM_REGISTRY_TOKEN` | Private npm packages (if used) | npm account → access tokens | 12 mo |
+| `PYPI_INDEX_URL` | Private PyPI (if used) | self-hosted index | per env |
+
+### GitHub Variables (per-repo)
+
+| Variable | Purpose |
+|----------|---------|
+| `STRYKER_DASHBOARD_PROJECT` | Project slug on the dashboard, e.g. `github.com/org/repo` |
+
+### Rotation procedure
+
+DevOps owns rotation. On expiry → create new token → update secret → trigger workflow → delete old. Logged in `docs/ops/secret-rotation-log.md`. Cross-ref `$deployment-ci-plan` § Secret management for the general baseline.
+
+### Local development
+
+Local mutation run without dashboard:
+```bash
+STRYKER_DASHBOARD_PROJECT=local npx stryker run --reporters html,progress
+```
+
+The dashboard reporter automatically skips if `STRYKER_DASHBOARD_API_KEY` is absent.
+
+---
+
+## 7. DoD
+
+### At production bootstrap (OPS gate)
+- [ ] `.stryker.conf.mjs` created with tier paths from `conductor.md § 2` + dashboard reporter
+- [ ] `mutmut.toml` created (if Python in project) + priority_paths for tier 1
+- [ ] `.github/workflows/mutation-testing.yml` created with JS+Python matrix + cron nightly + retention 30 days
+- [ ] `Mutation Testing / stryker` added to Required status checks
+- [ ] Secrets configured: `STRYKER_DASHBOARD_API_KEY` + variable `STRYKER_DASHBOARD_PROJECT`
+- [ ] `scripts/mutation-baseline-check.mjs` + `scripts/mutation_baseline_check.py` + `scripts/normalize-mutmut-to-aggregator.mjs` ready
+- [ ] `.mutation-baseline.json` initialised (empty `{}` or initial snapshot)
+- [ ] `$test-integrity-hooks-setup §4` aggregator parses `reports/mutation/*.json` — trial PR checked
+
+### During ongoing maintenance (TEST gate)
+- [ ] On CI failure from the mutation gate — open the Stryker HTML report and `$qa-mutation-testing §5` triage workflow
+- [ ] On baseline update — separate PR from the Tester with justification (not auto-merge)
+- [ ] Quarterly: review nightly full run trends on the dashboard; detected drift → ADR
+
+---
+
+## See also
+
+- `$qa-mutation-testing` — methodology + minimal-CI (this skill is the production complement to its §6)
+- `$qa-regression-baseline` — §7 TID baselines (mutation tracking) + baseline update procedure
+- `$qa-flaky-test-protocol` — prerequisite (mutation on flaky = false positives)
+- `$qa-property-based-testing` — complementary pillar 1 (property tests + mutation)
+- `$qa-test-integrity-audit` — static detector (together with mutation = full layer 2-3 defense)
+- `$testing-strategy-js` — §7 Mutation tier model (source of thresholds 80/60/optional)
+- `$tdd-workflow` — §1 Commit discipline tier 1-2 (RED/GREEN hashes coexist with the mutation gate)
+- `$tests-quality-review` — REV-side audit triggered by mutation findings
+- `$tests-integrity-rules` — SFS-side rules (forbidden patterns that mutation also catches)
+- `$test-integrity-hooks-setup` — §4 aggregator into which `stryker-report.json` + `mutmut-report.json` feed
+- `$deployment-ci-plan` — DevOps CI baseline into which this workflow plugs
+- `conductor.md` § Test Integrity Orchestration §2 — tier paths drive Stryker mutator scope + mutmut priority paths
+- `conductor.md` § Test Integrity Orchestration §3 — block-merge on mutation score regression
+- `reviewer.md` § Test-Code Co-Modification Audit — REV-side response to mutation survivors

package/domains/development/locales/en/.agents/skills/mutation-testing-setup/agents/claude.json

@@ -0,0 +1,19 @@
+{
+  "name": "mutation-testing-setup",
+  "display_name": "Mutation Testing Setup (DevOps + Tester)",
+  "description": "Production-grade wiring for mutation testing on CI/CD — Stryker (JS/TS) + mutmut (Python) with matrix parallel, PR incremental + nightly full run on cron, gh check Required status binding, tier-aware threshold gates (80%/60%/optional from $testing-strategy-js §7), Stryker dashboard secret management, output format for $test-integrity-hooks-setup §4 aggregator. Production complement to the minimal-CI workflow from $qa-mutation-testing §6. Activate at production repo bootstrap, when scaling minimal-CI to matrix, when adding nightly full run, when connecting to the test-integrity aggregator.",
+  "default_prompt": "Use $mutation-testing-setup when the task relates to the skill \"Mutation Testing Setup (DevOps + Tester)\".",
+  "triggers": [
+    "mutation-testing-setup",
+    "mutation testing setup",
+    "Mutation Testing Setup (DevOps + Tester)"
+  ],
+  "capabilities": [
+    "testing",
+    "ops",
+    "mutation",
+    "ci"
+  ],
+  "tools": [],
+  "implicit_invocation": true
+}

package/domains/development/locales/en/.agents/skills/mutation-testing-setup/agents/copilot.json

@@ -0,0 +1,19 @@
+{
+  "name": "mutation-testing-setup",
+  "display_name": "Mutation Testing Setup (DevOps + Tester)",
+  "description": "Production-grade wiring for mutation testing on CI/CD — Stryker (JS/TS) + mutmut (Python) with matrix parallel, PR incremental + nightly full run on cron, gh check Required status binding, tier-aware threshold gates (80%/60%/optional from $testing-strategy-js §7), Stryker dashboard secret management, output format for $test-integrity-hooks-setup §4 aggregator. Production complement to the minimal-CI workflow from $qa-mutation-testing §6. Activate at production repo bootstrap, when scaling minimal-CI to matrix, when adding nightly full run, when connecting to the test-integrity aggregator.",
+  "default_prompt": "Use $mutation-testing-setup when the task relates to the skill \"Mutation Testing Setup (DevOps + Tester)\".",
+  "triggers": [
+    "mutation-testing-setup",
+    "mutation testing setup",
+    "Mutation Testing Setup (DevOps + Tester)"
+  ],
+  "capabilities": [
+    "testing",
+    "ops",
+    "mutation",
+    "ci"
+  ],
+  "tools": [],
+  "implicit_invocation": true
+}

package/domains/development/locales/en/.agents/skills/mutation-testing-setup/agents/gemini.json

@@ -0,0 +1,19 @@
+{
+  "name": "mutation-testing-setup",
+  "display_name": "Mutation Testing Setup (DevOps + Tester)",
+  "description": "Production-grade wiring for mutation testing on CI/CD — Stryker (JS/TS) + mutmut (Python) with matrix parallel, PR incremental + nightly full run on cron, gh check Required status binding, tier-aware threshold gates (80%/60%/optional from $testing-strategy-js §7), Stryker dashboard secret management, output format for $test-integrity-hooks-setup §4 aggregator. Production complement to the minimal-CI workflow from $qa-mutation-testing §6. Activate at production repo bootstrap, when scaling minimal-CI to matrix, when adding nightly full run, when connecting to the test-integrity aggregator.",
+  "default_prompt": "Use $mutation-testing-setup when the task relates to the skill \"Mutation Testing Setup (DevOps + Tester)\".",
+  "triggers": [
+    "mutation-testing-setup",
+    "mutation testing setup",
+    "Mutation Testing Setup (DevOps + Tester)"
+  ],
+  "capabilities": [
+    "testing",
+    "ops",
+    "mutation",
+    "ci"
+  ],
+  "tools": [],
+  "implicit_invocation": true
+}

package/domains/development/locales/en/.agents/skills/mutation-testing-setup/agents/kimi.yaml

@@ -0,0 +1,15 @@
+name: "mutation-testing-setup"
+display_name: "Mutation Testing Setup (DevOps + Tester)"
+description: "Production-grade wiring for mutation testing on CI/CD — Stryker (JS/TS) + mutmut (Python) with matrix parallel, PR incremental + nightly full run on cron, gh check Required status binding, tier-aware threshold gates (80%/60%/optional from $testing-strategy-js §7), Stryker dashboard secret management, output format for $test-integrity-hooks-setup §4 aggregator. Production complement to the minimal-CI workflow from $qa-mutation-testing §6. Activate at production repo bootstrap, when scaling minimal-CI to matrix, when adding nightly full run, when connecting to the test-integrity aggregator."
+default_prompt: "Use $mutation-testing-setup when the task relates to the skill \"Mutation Testing Setup (DevOps + Tester)\"."
+triggers:
+  - "mutation-testing-setup"
+  - "mutation testing setup"
+  - "Mutation Testing Setup (DevOps + Tester)"
+capabilities:
+  - "testing"
+  - "ops"
+  - "mutation"
+  - "ci"
+tools: []
+implicit_invocation: true

package/domains/development/locales/en/.agents/skills/mutation-testing-setup/agents/openai.yaml

@@ -0,0 +1,8 @@
+interface:
+  display_name: "Mutation Testing Setup (DevOps + Tester)"
+  short_description: "Production-grade wiring for mutation testing on CI/CD — Stryker (JS/TS) + mutmut (Python) with matrix parallel, PR..."
+  default_prompt: "Use $mutation-testing-setup when the task relates to the skill \"Mutation Testing Setup (DevOps + Tester)\"."
+dependencies:
+  tools: []
+policy:
+  allow_implicit_invocation: true

package/domains/development/locales/en/.agents/skills/mutation-testing-setup/agents/qwen.json

@@ -0,0 +1,19 @@
+{
+  "name": "mutation-testing-setup",
+  "display_name": "Mutation Testing Setup (DevOps + Tester)",
+  "description": "Production-grade wiring for mutation testing on CI/CD — Stryker (JS/TS) + mutmut (Python) with matrix parallel, PR incremental + nightly full run on cron, gh check Required status binding, tier-aware threshold gates (80%/60%/optional from $testing-strategy-js §7), Stryker dashboard secret management, output format for $test-integrity-hooks-setup §4 aggregator. Production complement to the minimal-CI workflow from $qa-mutation-testing §6. Activate at production repo bootstrap, when scaling minimal-CI to matrix, when adding nightly full run, when connecting to the test-integrity aggregator.",
+  "default_prompt": "Use $mutation-testing-setup when the task relates to the skill \"Mutation Testing Setup (DevOps + Tester)\".",
+  "triggers": [
+    "mutation-testing-setup",
+    "mutation testing setup",
+    "Mutation Testing Setup (DevOps + Tester)"
+  ],
+  "capabilities": [
+    "testing",
+    "ops",
+    "mutation",
+    "ci"
+  ],
+  "tools": [],
+  "implicit_invocation": true
+}

package/domains/development/locales/en/.agents/skills/mutation-testing-setup/agents/skill.yaml

@@ -0,0 +1,23 @@
+version: 1
+name: "mutation-testing-setup"
+display_name: "Mutation Testing Setup (DevOps + Tester)"
+description: "Production-grade wiring for mutation testing on CI/CD — Stryker (JS/TS) + mutmut (Python) with matrix parallel, PR incremental + nightly full run on cron, gh check Required status binding, tier-aware threshold gates (80%/60%/optional from $testing-strategy-js §7), Stryker dashboard secret management, output format for $test-integrity-hooks-setup §4 aggregator. Production complement to the minimal-CI workflow from $qa-mutation-testing §6. Activate at production repo bootstrap, when scaling minimal-CI to matrix, when adding nightly full run, when connecting to the test-integrity aggregator."
+default_prompt: "Use $mutation-testing-setup when the task relates to the skill \"Mutation Testing Setup (DevOps + Tester)\"."
+triggers:
+  - "mutation-testing-setup"
+  - "mutation testing setup"
+  - "Mutation Testing Setup (DevOps + Tester)"
+capabilities:
+  - "testing"
+  - "ops"
+  - "mutation"
+  - "ci"
+tools: []
+invocation:
+  explicit: true
+  implicit: true
+localization:
+  default_locale: "ru"
+  available_locales:
+    - "ru"
+    - "en"