Add mutation-testing-rollout skill#73
Draft
leynos wants to merge 2 commits into
Draft
Conversation
Distil the estate-wide mutation-testing programme into a reusable skill: per-repository adoption of the shared `mutation-cargo`/ `mutation-mutmut` callers, baseline verification under the mutation runner's conditions (nextest isolation, doctest blind spots, the mutmut sandbox), contract-test conventions (shape-only SHA pinning), survivor triage discipline, run sweeps, and the hard-won estate lessons (unpinned-linter drift, stale checkouts, false survivors from companion crates). `install-skills` picks the new directory up automatically; no registration is required.
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
The first estate sweep disproved wall-clock duration as a triage signal (runner-queue wait inflates 15-second no-ops to an hour) and surfaced two silent-suppression traps and the change-detection gate's coverage suppression. Key sweeps on `mutation_detect_has_changes` and the mutants job conclusion instead, verify suppressions by scoped re-run, and dispatch a full run after merging a baseline fix rather than waiting for the schedule.
leynos
force-pushed
the
skills/mutation-testing-rollout
branch
from
July 20, 2026 14:42
907affe to
cadf0a8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This branch adds a new skill,
skills/mutation-testing-rollout/, capturing theprocess used to roll scheduled, informational mutation testing out across the
github.com/leynos/* estate and to operate it afterwards. It covers the
architecture (thin per-repository callers of the shared
mutation-cargo.yml/mutation-mutmut.ymlreusable workflows, SHA-pinned andDependabot-owned), the per-repository adoption recipe with the baseline
hazards found in practice (nextest isolation, doctest blind spots, the mutmut
sandbox, workflow-source tree pollution, stateful test dependencies), the
contract-test conventions (shape-only SHA assertions), the survivor-triage
discipline (issues per area, killing tests over skips, dead-code deletion,
kill-site traceability), run-sweep operation, and the estate lessons
(unpinned-linter drift, stale local checkouts, companion-crate false
survivors).
install-skillscopies every directory underskills/automatically, so noregistration is needed.
Review walkthrough
skills/mutation-testing-rollout/SKILL.md,
following the repository's existing
description:frontmatter + directiveprose convention (compare
skills/rebase/SKILL.md).
Validation
markdownlint(repository script) on the new file: 0 errorstypos --config typos.tomlon the new file: clean (en-GB Oxford-ize)Notes
The content distils the rollout tracked in the estate's mutation-testing
rollout plan; it is written to be applied to any comparable estate, not only
the current one.