[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79XMMFJ3SGGAN0RRY1ZMAGM":3,"skill-same:01M79XMMFJ3SGGAN0RRY1ZMAGM":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M79XMMFJ3SGGAN0RRY1ZMAGM","deniz-dotnet-general.test-gap-analysis",null,"Performs report-only pseudo-mutation analysis of existing tests: find caller-visible production-code changes that current assertions would not catch. Use when asked whether a bug or mutation could survive, where tests are behaviorally blind, or which production outcomes lack protection. Polyglot. DO NOT USE FOR: writing tests, proof that tests catch an identified fix or feature (test-value-evidence), suite organization or taxonomy, coverage\u002FCRAP interpretation, assertion\u002Fsmell audits, or running a mutation-testing tool.","Blind-Striker\u002Fagent-skills-and-plugins","Blind-Striker","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1965259?v=4","01M79WFXTE5PH0C1VB7B54ANMN","Deniz İrgin","01M79WFXV5KZ5GST1K8G035DM5",1,"MIT","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fopencode\u002Fdeniz-dotnet-general\u002Fskills\u002Fdeniz-dotnet-general.test-gap-analysis\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: deniz-dotnet-general.test-gap-analysis\ndescription: \"Performs report-only pseudo-mutation analysis of existing tests:\n  find caller-visible production-code changes that current assertions would not\n  catch. Use when asked whether a bug or mutation could survive, where tests are\n  behaviorally blind, or which production outcomes lack protection. Polyglot. DO\n  NOT USE FOR: writing tests, proof that tests catch an identified fix or\n  feature (test-value-evidence), suite organization or taxonomy, coverage\u002FCRAP\n  interpretation, assertion\u002Fsmell audits, or running a mutation-testing tool.\"\n---\n\n# Test Gap Analysis\n\nAnswer one question: **which caller-visible production behaviors could change\nwithout an existing test failing?** Mutation reasoning is a probe, not the goal.\nInventory public outcomes first, then verify only credible gaps.\n\n## Decision flow\n\n### 1. Set scope\n\nDiscover production and test files from manifests and file types. After a narrow\nsearch misses, inspect the current directory broadly before asking for paths.\n\n| Request | Action |\n|---|---|\n| One component or named risk | Inventory every high-risk public outcome in scope; do not edit production code unless verification was requested |\n| General small-component review | Inventory distinct outcomes and report caller-visible gaps from source\u002Fassertion mapping |\n| Explicit survivor verification | Inventory all requested outcomes; execute one representative observable candidate for each distinct high-risk outcome under verification, then classify it as **Survived** or **Killed** |\n| Explicit exhaustive audit | Read [references\u002Fmutation-catalog.md](references\u002Fmutation-catalog.md) and classify all meaningful candidates |\n| Add or create tests | Report the verified gaps; test writing is outside this skill |\n\nWhen the request names a risk, turn it into a one-line public-outcome allowlist\nbefore reading code. An outcome is not in scope merely because the same method writes it.\nFor `money math`, allow computed or returned amounts, rates, tier\u002Fboundary\nchoice, percentage base\u002Forder, floors\u002Fcaps, and rounding; exclude non-monetary\nstate predicates (including derived booleans), identity, and formatting. Private\ncode is in scope only to trace an allowed outcome.\n\nDo not expand a focused request into a repository audit, plan artifact, or\ndashboard. Use source and tests directly for familiar frameworks. When discovery\nor assertion semantics are unclear, load the `deniz-dotnet-general.test-analysis-extensions`\nskill and read its matching language file; do not search installation\ndirectories. If it is absent, state the limitation and use the pinned APIs and\nrules here.\n\n### 2. Establish one baseline\n\nFor a source-only advisory review, skip execution and label empirical survival\nunverified. A baseline is required when the user requests execution or survivor\nverification. Run the narrowest existing test command once. Choose it from the project\nmanifest; Microsoft.Testing.Platform executables may require `dotnet run`.\nConfirm tests executed: exit 0 with build-only output is not green. If that one\nattempt cannot run the suite, do not troubleshoot the runner or try alternate\ncommands for an advisory review; continue statically and label all candidates\n**unverified**. Do not infer a project-configuration cause from missing output;\nname a cause only when the command reports it.\n\nMissing runner output limits only claims of empirical mutation survival. It does\nnot make source-proven facts tentative: a public outcome with no reaching test\nis still **No coverage**, and an exact expected value derived from the\nunmodified implementation is still actionable. State the baseline limitation\nonce, then give the static source\u002Fassertion conclusion directly instead of\nhedging every row.\n\nFor an advisory review such as \"would tests catch this?\", stop execution after\nthat baseline. Source-to-assertion mapping is sufficient evidence for **No\ncoverage** and **Candidate survivor (unverified)**. Trace or run the unmodified\ncode once only when an original value is unclear. Apply mutations only for\nexplicit verification or an exhaustive audit.\n\nAny focused mutation budget limits execution, not discovery. Keep every\ndistinct unasserted public outcome in the inventory.\n\n### 3. Inventory public outcomes\n\nFor each public entry point, map:\n\n- input partitions: classifier arms, compound conditions, invalid and\n  nearest-valid guard boundaries, and default cases;\n- each independent observation: returned field\u002Fvariant, exception type,\n  invalid-input acceptance, public state transition, or external side effect;\n- private-helper composition, constants\u002Frates, rounding, retries, cancellation,\n  and error propagation as observed through the public caller.\n\nUse `public input\u002Fsequence -> expected outcome -> existing assertion -> gap`.\nOne asserted return field does not cover another. One allowed result does not\ncover its denial.\n\n**Money math:** inventory the no-op path, every rate\u002Ftier and exact boundary,\noperation order, percentage base or composition, floor\u002Fcap, and rounding. Trace\nprivate helpers through the public result. A test asserting only a broad range\ndoes not pin any exact amount. For each actionable money row, derive one witness\ninput and its exact original result through the complete call chain; do not\nrecommend a generic \"assert the exact amount\" without supplying that amount.\n\n**Ordered guards and retries:** inventory `invalid below minimum | first valid |\nlast allowed or retryable | first blocked | later blocked`. For an upper guard\nsuch as `value >= limit`, use `limit - 1`, `limit`, and `limit + 1`; the last\nwitness exposes narrowing to `value == limit`. Inventory every accepted and\nrejected error class. When type matching is polymorphic, include a representative\nderived accepted type that would expose exact-runtime-type narrowing. A test at\nthe first blocked value does not protect the last allowed or later blocked value.\n\n**Authorization:** enumerate each relevant identity\u002Frole, resource class, and\naction from the caller's view. Untested `false`, forbidden, and unchanged-role\noutcomes are first-class security gaps. Do not analyze variants of an allowed\npath while a denial outcome remains uninventoried. Check each public surface:\n\n- permission-returning APIs: every distinct role\u002Fresource class and every\n  returned capability independently;\n- action-dispatch APIs: each read\u002Fwrite\u002Fdelete-style action branch, especially\n  paths that must return denial;\n- role\u002Fstate transitions: accepted, rejected, invalid, null, and empty inputs,\n  including outcomes that must leave state unchanged.\n\nReserve execution for wholly untested public branches before another variant\nof a partially covered helper. If more than five high-risk behaviors are\nunasserted, execute the top 3-5 and keep the rest visible as **No coverage** or\n**Candidate survivor (unverified)**.\n\nExecution never replaces the ledger. Before mutating or answering, classify\nevery required outcome, including each invalid input, guard boundary,\nclassifier arm, action, and denial.\n\n**Completeness checkpoint:** before selecting findings, explicitly account for\nevery independent mode\u002Fflag, both zero and negative for a `\u003C= 0` guard, every\naccepted exception class, and a representative derived accepted exception when\nmatching is polymorphic. For a removed guard, trace the fallthrough: if it still\nproduces the same public exception type, it is equivalent unless finer exception\nmetadata is an established contract.\n\n### 4. Admit only observable candidates\n\nFirst replay each exact mutation against every existing asserted input or\nsequence with all arguments fixed. Any changed return, exception, state, or side\neffect is **Likely killed**; a dedicated single-purpose test is unnecessary.\nNever compare the mutant on one input with the original on another.\n\nFor survivors, choose a witness before execution or reporting and state\n`witness -> original observation -> mutant observation`. Reuse it in the\nsmallest test. Admit it only when the last two differ publicly after tracing the\nfull call chain; otherwise choose a distinguishing witness or drop it.\n\nExclude:\n\n- edits that require inserting or reordering statements rather than changing or\n  removing an existing expression, condition, constant, return, or side effect;\n- edits that do not compile, including removal of a declaration whose value is\n  still referenced;\n- overflow behavior, exception message\u002F`ParamName` metadata, or other semantics\n  not established by the current contract, source intent, or tests;\n- a removed guard or short-circuit that falls through to the same result,\n  exception, state, and side effects;\n- private representation changes that every public input sequence observes\n  identically, even if the suite stays green;\n- a mutation whose proposed test passes against both original and mutant;\n- boundary edits that return the same value on the distinguishing input; for\n  example, changing `result \u003C floor ? floor : result` to `\u003C=` is equivalent at\n  equality because both branches return `floor`;\n- a standalone auto-property or trivial one-line wrapper\u002Fpredicate with no\n  meaningful branch, calculation, or side effect, unless the user names it;\n- hypothetical future impact, generated code, logging\u002Fformatting-only changes,\n  impossible values, and duplicate syntax variants.\n\nMissing direct assertions do not prove **No coverage**: first trace existing\nassertions through public callers and shared branches. Missing assertions make\nan **observable** candidate a survivor; they do not make an inert mutation\nmeaningful.\n\n### 5. Rank and classify\n\nRank: (1) security denials, financial outcomes, errors, and state changes;\n(2) wholly unasserted public outcomes; (3) boundaries or exact values reached by\nweak assertions; (4) alternate variants of already-asserted behavior.\n\nFinish the inventory before selecting mutations or a verdict. One killed\nattempt, exception type, or switch arm does not clear its siblings.\n\nChoose the verdict from the completed inventory:\n\n- **Strong** when core branches and primary boundaries are protected and only a\n  few validation or default-case variants remain;\n- **Mixed** when meaningful coverage exists but at least one important outcome\n  partition is unprotected;\n- **Weak** when important outcomes are broadly unprotected.\n\nA handful of validation gaps does not make an otherwise broad suite **Mixed**\nunless validation is the named risk or the gaps threaten security, data, or\nother contract-critical behavior.\n\nWhen the inventory meets the **Strong** criteria above, lead with **Strong** and\nname the protected boundaries and dual assertions before listing minor gaps. Do\nnot open with `Mixed`, \"only core paths\", or a risk-heavy dashboard.\n\nStop when existing assertions kill the remaining candidates or no credible\npublic survivor remains. Do not mutate every operator merely to fill a report or\ncalculate a score.\n\n| Result | Meaning |\n|---|---|\n| **Likely killed** | An existing assertion observes the changed outcome |\n| **Candidate survivor (unverified)** | Observable change appears unasserted; not executed |\n| **Killed** | Exact observable mutation executed and a relevant assertion failed |\n| **Survived** | Exact observable mutation executed and tests stayed green |\n| **No coverage** | No test reaches the public outcome; report the missing branch without inventing a survivor |\n| **Equivalent** | No public observation changes; omit from findings |\n\nOutside explicit verification or an exhaustive audit, execute no mutations. Do\nnot mutate to confirm obvious no coverage.\nFor explicit verification, execute one representative candidate per distinct\nhigh-risk outcome in scope; do not stop after the first one or two while another\nguard, action branch, error class, or denial remains unclassified. Omit\nequivalent syntax variants.\n\n### 6. Verify without creating false positives\n\nEnter this phase only for explicit verification or an exhaustive audit.\n\n1. Apply one candidate and confirm the diff changes exactly one intended\n   expression.\n2. Run the narrowest covering test and confirm tests executed: green means\n   **Survived**; a failure at a relevant assertion means **Killed**, for that\n   edit only. Build, discovery, infrastructure, or unrelated failures leave\n   the candidate **unverified**, not Killed.\n3. Revert immediately and confirm the clean source\u002Ftest baseline.\n4. After a green run, re-check the public counterfactual. Execution proves the\n   suite missed the edit, not that the edit changes behavior; drop inert or\n   unobservable mutants.\n\nNever leave mutations in the workspace. Before reporting, reconcile every\nunasserted high-risk outcome as **Survived**, **Candidate survivor\n(unverified)**, **No coverage**, or omitted **Equivalent**. Stop when no credible\npublic gap remains; do not fill a report with internal details or calculate a\nscore unless the user requested an exhaustive audit.\n\n## Output contract\n\nScale the response to the request.\n\nFor focused or small analysis, return:\n\n1. A one-line verdict: **Strong**, **Mixed**, or **Weak**, with the reason.\n2. For a **Strong** suite, one short strengths sentence naming the concrete\n   protected boundaries, guards, or paired observations that justify the verdict.\n3. One compact row per actionable **Survived**, **Candidate survivor\n   (unverified)**, or **No coverage** outcome. Before adding a row, apply the\n   outcome allowlist when the request names a risk, then apply the\n   observable-candidate rules; omit any candidate that fails either filter.\n   Include every high-risk outcome, use one row per distinct public outcome, and\n   consolidate only related low-risk variants:\n\n   | Risk | Public outcome | Change | Result\u002Fevidence | Smallest test |\n   |---|---|---|---|---|\n\n   Every gap needs a distinguishing witness and a concrete smallest test. An\n   error-path gap must name an invalid input and the expected error\u002Fresult.\n\n4. For a **Mixed** or **Weak** suite, one short strengths sentence naming\n   important killed behavior.\n5. When the request names exclusions, one short scope sentence naming the\n   generated, trivial, or unrelated code intentionally skipped.\n\nDo not repeat the table in prose or report discarded mutants, tool chronology,\nor in-flight reasoning.\n\nFor an exhaustive audit, separate executed **Killed \u002F Survived** counts from\nstatic **Likely killed \u002F Candidate survivor (unverified)** classifications and\n**No coverage \u002F Equivalent** inventory counts. Never include static reasoning\nin an empirical killed\u002Ftotal ratio. Group findings by risk.\n\n## Reliability rules\n\n- A passing test that does not assert the changed outcome does not kill a\n  mutation.\n- Coverage is per behavior partition. One switch\u002Fternary arm or compound input\n  does not prove siblings: allow does not prove deny; read does not prove write;\n  null does not prove empty or whitespace when those inputs have different\n  caller-visible outcomes. A kill clears only the edit and path that ran.\n- Private helpers reached through a public method remain in scope.\n- Error semantics are language-specific: in Rust, `?` propagation versus panic\n  is observable behavior; in C#, exception type and whether an input guard\n  accepts or rejects a value are observable behavior.\n- Cross-check every exact amount or boundary result against the unmodified\n  implementation or an existing exact assertion. If it cannot be checked,\n  state the behavioral relation without inventing a number.\n- Do not label a finding high-risk merely because a mutation survived.\n- Never recommend a redundant test for behavior the existing suite already\n  protects.\n\n## Validation\n\n- [ ] Scope stayed proportional to the request\n- [ ] The original suite passed, or static-only limits are explicit\n- [ ] Every high-risk public outcome in scope was inventoried\n- [ ] Original and mutant have different caller-visible observations\n- [ ] Every outcome labeled **Survived** was executed; unexecuted candidates use\n      **Candidate survivor (unverified)**\n- [ ] Every temporary mutation was reverted\n- [ ] Findings exclude trivial, generated, and equivalent changes\n- [ ] Recommendations target only demonstrated gaps\n- [ ] Every public entry-point branch and each accepted exception type in scope\n      is explicitly accounted for\n","# Test Gap Analysis\n\nAnswer one question: **which caller-visible production behaviors could change\nwithout an existing test failing?** Mutation reasoning is a probe, not the goal.\nInventory public outcomes first, then verify only credible gaps.\n\n## Decision flow\n\n### 1. Set scope\n\nDiscover production and test files from manifests and file types. After a narrow\nsearch misses, inspect the current directory broadly before asking for paths.\n\n| Request | Action |\n|---|---|\n| One component or named risk | Inventory every high-risk public outcome in scope; do not edit production code unless verification was requested |\n| General small-component review | Inventory distinct outcomes and report caller-visible gaps from source\u002Fassertion mapping |\n| Explicit survivor verification | Inventory all requested outcomes; execute one representative observable candidate for each distinct high-risk outcome under verification, then classify it as **Survived** or **Killed** |\n| Explicit exhaustive audit | Read [references\u002Fmutation-catalog.md](references\u002Fmutation-catalog.md) and classify all meaningful candidates |\n| Add or create tests | Report the verified gaps; test writing is outside this skill |\n\nWhen the request names a risk, turn it into a one-line public-outcome allowlist\nbefore reading code. An outcome is not in scope merely because the same method writes it.\nFor `money math`, allow computed or returned amounts, rates, tier\u002Fboundary\nchoice, percentage base\u002Forder, floors\u002Fcaps, and rounding; exclude non-monetary\nstate predicates (including derived booleans), identity, and formatting. Private\ncode is in scope only to trace an allowed outcome.\n\nDo not expand a focused request into a repository audit, plan artifact, or\ndashboard. Use source and tests directly for familiar frameworks. When discovery\nor assertion semantics are unclear, load the `deniz-dotnet-general.test-analysis-extensions`\nskill and read its matching language file; do not search installation\ndirectories. If it is absent, state the limitation and use the pinned APIs and\nrules here.\n\n### 2. Establish one baseline\n\nFor a source-only advisory review, skip execution and label empirical survival\nunverified. A baseline is required when the user requests execution or survivor\nverification. Run the narrowest existing test command once. Choose it from the project\nmanifest; Microsoft.Testing.Platform executables may require `dotnet run`.\nConfirm tests executed: exit 0 with build-only output is not green. If that one\nattempt cannot run the suite, do not troubleshoot the runner or try alternate\ncommands for an advisory review; continue statically and label all candidates\n**unverified**. Do not infer a project-configuration cause from missing output;\nname a cause only when the command reports it.\n\nMissing runner output limits only claims of empirical mutation survival. It does\nnot make source-proven facts tentative: a public outcome with no reaching test\nis still **No coverage**, and an exact expected value derived from the\nunmodified implementation is still actionable. State the baseline limitation\nonce, then give the static source\u002Fassertion conclusion directly instead of\nhedging every row.\n\nFor an advisory review such as \"would tests catch this?\", stop execution after\nthat baseline. Source-to-assertion mapping is sufficient evidence for **No\ncoverage** and **Candidate survivor (unverified)**. Trace or run the unmodified\ncode once only when an original value is unclear. Apply mutations only for\nexplicit verification or an exhaustive audit.\n\nAny focused mutation budget limits execution, not discovery. Keep every\ndistinct unasserted public outcome in the inventory.\n\n### 3. Inventory public outcomes\n\nFor each public entry point, map:\n\n- input partitions: classifier arms, compound conditions, invalid and\n  nearest-valid guard boundaries, and default cases;\n- each independent observation: returned field\u002Fvariant, exception type,\n  invalid-input acceptance, public state transition, or external side effect;\n- private-helper composition, constants\u002Frates, rounding, retries, cancellation,\n  and error propagation as observed through the public caller.\n\nUse `public input\u002Fsequence -> expected outcome -> existing assertion -> gap`.\nOne asserted return field does not cover another. One allowed result does not\ncover its denial.\n\n**Money math:** inventory the no-op path, every rate\u002Ftier and exact boundary,\noperation order, percentage base or composition, floor\u002Fcap, and rounding. Trace\nprivate helpers through the public result. A test asserting only a broad range\ndoes not pin any exact amount. For each actionable money row, derive one witness\ninput and its exact original result through the complete call chain; do not\nrecommend a generic \"assert the exact amount\" without supplying that amount.\n\n**Ordered guards and retries:** inventory `invalid below minimum | first valid |\nlast allowed or retryable | first blocked | later blocked`. For an upper guard\nsuch as `value >= limit`, use `limit - 1`, `limit`, and `limit + 1`; the last\nwitness exposes narrowing to `value == limit`. Inventory every accepted and\nrejected error class. When type matching is polymorphic, include a representative\nderived accepted type that would expose exact-runtime-type narrowing. A test at\nthe first blocked value does not protect the last allowed or later blocked value.\n\n**Authorization:** enumerate each relevant identity\u002Frole, resource class, and\naction from the caller's view. Untested `false`, forbidden, and unchanged-role\noutcomes are first-class security gaps. Do not analyze variants of an allowed\npath while a denial outcome remains uninventoried. Check each public surface:\n\n- permission-returning APIs: every distinct role\u002Fresource class and every\n  returned capability independently;\n- action-dispatch APIs: each read\u002Fwrite\u002Fdelete-style action branch, especially\n  paths that must return denial;\n- role\u002Fstate transitions: accepted, rejected, invalid, null, and empty inputs,\n  including outcomes that must leave state unchanged.\n\nReserve execution for wholly untested public branches before another variant\nof a partially covered helper. If more than five high-risk behaviors are\nunasserted, execute the top 3-5 and keep the rest visible as **No coverage** or\n**Candidate survivor (unverified)**.\n\nExecution never replaces the ledger. Before mutating or answering, classify\nevery required outcome, including each invalid input, guard boundary,\nclassifier arm, action, and denial.\n\n**Completeness checkpoint:** before selecting findings, explicitly account for\nevery independent mode\u002Fflag, both zero and negative for a `\u003C= 0` guard, every\naccepted exception class, and a representative derived accepted exception when\nmatching is polymorphic. For a removed guard, trace the fallthrough: if it still\nproduces the same public exception type, it is equivalent unless finer exception\nmetadata is an established contract.\n\n### 4. Admit only observable candidates\n\nFirst replay each exact mutation against every existing asserted input or\nsequence with all arguments fixed. Any changed return, exception, state, or side\neffect is **Likely killed**; a dedicated single-purpose test is unnecessary.\nNever compare the mutant on one input with the original on another.\n\nFor survivors, choose a witness before execution or reporting and state\n`witness -> original observation -> mutant observation`. Reuse it in the\nsmallest test. Admit it only when the last two differ publicly after tracing the\nfull call chain; otherwise choose a distinguishing witness or drop it.\n\nExclude:\n\n- edits that require inserting or reordering statements rather than changing or\n  removing an existing expression, condition, constant, return, or side effect;\n- edits that do not compile, including removal of a declaration whose value is\n  still referenced;\n- overflow behavior, exception message\u002F`ParamName` metadata, or other semantics\n  not established by the current contract, source intent, or tests;\n- a removed guard or short-circuit that falls through to the same result,\n  exception, state, and side effects;\n- private representation changes that every public input sequence observes\n  identically, even if the suite stays green;\n- a mutation whose proposed test passes against both original and mutant;\n- boundary edits that return the same value on the distinguishing input; for\n  example, changing `result \u003C floor ? floor : result` to `\u003C=` is equivalent at\n  equality because both branches return `floor`;\n- a standalone auto-property or trivial one-line wrapper\u002Fpredicate with no\n  meaningful branch, calculation, or side effect, unless the user names it;\n- hypothetical future impact, generated code, logging\u002Fformatting-only changes,\n  impossible values, and duplicate syntax variants.\n\nMissing direct assertions do not prove **No coverage**: first trace existing\nassertions through public callers and shared branches. Missing assertions make\nan **observable** candidate a survivor; they do not make an inert mutation\nmeaningful.\n\n### 5. Rank and classify\n\nRank: (1) security denials, financial outcomes, errors, and state changes;\n(2) wholly unasserted public outcomes; (3) boundaries or exact values reached by\nweak assertions; (4) alternate variants of already-asserted behavior.\n\nFinish the inventory before selecting mutations or a verdict. One killed\nattempt, exception type, or switch arm does not clear its siblings.\n\nChoose the verdict from the completed inventory:\n\n- **Strong** when core branches and primary boundaries are protected and only a\n  few validation or default-case variants remain;\n- **Mixed** when meaningful coverage exists but at least one important outcome\n  partition is unprotected;\n- **Weak** when important outcomes are broadly unprotected.\n\nA handful of validation gaps does not make an otherwise broad suite **Mixed**\nunless validation is the named risk or the gaps threaten security, data, or\nother contract-critical behavior.\n\nWhen the inventory meets the **Strong** criteria above, lead with **Strong** and\nname the protected boundaries and dual assertions before listing minor gaps. Do\nnot open with `Mixed`, \"only core paths\", or a risk-heavy dashboard.\n\nStop when existing assertions kill the remaining candidates or no credible\npublic survivor remains. Do not mutate every operator merely to fill a report or\ncalculate a score.\n\n| Result | Meaning |\n|---|---|\n| **Likely killed** | An existing assertion observes the changed outcome |\n| **Candidate survivor (unverified)** | Observable change appears unasserted; not executed |\n| **Killed** | Exact observable mutation executed and a relevant assertion failed |\n| **Survived** | Exact observable mutation executed and tests stayed green |\n| **No coverage** | No test reaches the public outcome; report the missing branch without inventing a survivor |\n| **Equivalent** | No public observation changes; omit from findings |\n\nOutside explicit verification or an exhaustive audit, execute no mutations. Do\nnot mutate to confirm obvious no coverage.\nFor explicit verification, execute one representative candidate per distinct\nhigh-risk outcome in scope; do not stop after the first one or two while another\nguard, action branch, error class, or denial remains unclassified. Omit\nequivalent syntax variants.\n\n### 6. Verify without creating false positives\n\nEnter this phase only for explicit verification or an exhaustive audit.\n\n1. Apply one candidate and confirm the diff changes exactly one intended\n   expression.\n2. Run the narrowest covering test and confirm tests executed: green means\n   **Survived**; a failure at a relevant assertion means **Killed**, for that\n   edit only. Build, discovery, infrastructure, or unrelated failures leave\n   the candidate **unverified**, not Killed.\n3. Revert immediately and confirm the clean source\u002Ftest baseline.\n4. After a green run, re-check the public counterfactual. Execution proves the\n   suite missed the edit, not that the edit changes behavior; drop inert or\n   unobservable mutants.\n\nNever leave mutations in the workspace. Before reporting, reconcile every\nunasserted high-risk outcome as **Survived**, **Candidate survivor\n(unverified)**, **No coverage**, or omitted **Equivalent**. Stop when no credible\npublic gap remains; do not fill a report with internal details or calculate a\nscore unless the user requested an exhaustive audit.\n\n## Output contract\n\nScale the response to the request.\n\nFor focused or small analysis, return:\n\n1. A one-line verdict: **Strong**, **Mixed**, or **Weak**, with the reason.\n2. For a **Strong** suite, one short strengths sentence naming the concrete\n   protected boundaries, guards, or paired observations that justify the verdict.\n3. One compact row per actionable **Survived**, **Candidate survivor\n   (unverified)**, or **No coverage** outcome. Before adding a row, apply the\n   outcome allowlist when the request names a risk, then apply the\n   observable-candidate rules; omit any candidate that fails either filter.\n   Include every high-risk outcome, use one row per distinct public outcome, and\n   consolidate only related low-risk variants:\n\n   | Risk | Public outcome | Change | Result\u002Fevidence | Smallest test |\n   |---|---|---|---|---|\n\n   Every gap needs a distinguishing witness and a concrete smallest test. An\n   error-path gap must name an invalid input and the expected error\u002Fresult.\n\n4. For a **Mixed** or **Weak** suite, one short strengths sentence naming\n   important killed behavior.\n5. When the request names exclusions, one short scope sentence naming the\n   generated, trivial, or unrelated code intentionally skipped.\n\nDo not repeat the table in prose or report discarded mutants, tool chronology,\nor in-flight reasoning.\n\nFor an exhaustive audit, separate executed **Killed \u002F Survived** counts from\nstatic **Likely killed \u002F Candidate survivor (unverified)** classifications and\n**No coverage \u002F Equivalent** inventory counts. Never include static reasoning\nin an empirical killed\u002Ftotal ratio. Group findings by risk.\n\n## Reliability rules\n\n- A passing test that does not assert the changed outcome does not kill a\n  mutation.\n- Coverage is per behavior partition. One switch\u002Fternary arm or compound input\n  does not prove siblings: allow does not prove deny; read does not prove write;\n  null does not prove empty or whitespace when those inputs have different\n  caller-visible outcomes. A kill clears only the edit and path that ran.\n- Private helpers reached through a public method remain in scope.\n- Error semantics are language-specific: in Rust, `?` propagation versus panic\n  is observable behavior; in C#, exception type and whether an input guard\n  accepts or rejects a value are observable behavior.\n- Cross-check every exact amount or boundary result against the unmodified\n  implementation or an existing exact assertion. If it cannot be checked,\n  state the behavioral relation without inventing a number.\n- Do not label a finding high-risk merely because a mutation survived.\n- Never recommend a redundant test for behavior the existing suite already\n  protects.\n\n## Validation\n\n- [ ] Scope stayed proportional to the request\n- [ ] The original suite passed, or static-only limits are explicit\n- [ ] Every high-risk public outcome in scope was inventoried\n- [ ] Original and mutant have different caller-visible observations\n- [ ] Every outcome labeled **Survived** was executed; unexecuted candidates use\n      **Candidate survivor (unverified)**\n- [ ] Every temporary mutation was reverted\n- [ ] Findings exclude trivial, generated, and equivalent changes\n- [ ] Recommendations target only demonstrated gaps\n- [ ] Every public entry-point branch and each accepted exception type in scope\n      is explicitly accounted for\n",{"name":5,"description":7},"master","b30b1c1908dbc56a8184128f18803053d762ccb5","opencode\u002Fdeniz-dotnet-general\u002Fskills\u002Fdeniz-dotnet-general.test-gap-analysis",0,"https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins","https:\u002F\u002Fgithub.com\u002FBlind-Striker","denizirgin.com","VP of Engineering - \r\n@armutcom @homeruntech @prontopro\r\n |  Speaker \r\n@CodeFiction\r\n, http:\u002F\u002Fcodefiction.tech | Developer, gamer, blogger, maiden iron fan","2026-11-13 00:23:18",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Blind-Striker\u002Fagent-skills-and-plugins --skill deniz-dotnet-general.test-gap-analysis",{"tool":39,"command":40},"bunx","bunx skills add Blind-Striker\u002Fagent-skills-and-plugins --skill deniz-dotnet-general.test-gap-analysis",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Blind-Striker\u002Fagent-skills-and-plugins --skill deniz-dotnet-general.test-gap-analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fopencode\u002Fdeniz-dotnet-general\u002Fskills\u002Fdeniz-dotnet-general.test-gap-analysis\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fmutation-catalog.md","REFERENCE","参考文档",3812,"https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fopencode\u002Fdeniz-dotnet-general\u002Fskills\u002Fdeniz-dotnet-general.test-gap-analysis\u002Freferences\u002Fmutation-catalog.md",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79YGWBJ52PHMSTKJ3RJ3AWR","writing-tunit-tests","Write tests in TUnit — the attributes, the async assertion model, data-driven cases, lifecycle hooks, and the parallelism rules. USE FOR writing or fixing a test in a TUnit project, translating a test idea into TUnit syntax, or reviewing TUnit test code for API mistakes. DO NOT USE FOR deciding what to test, judging whether a test is any good, or running tests.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-dotnet-general\u002Fwriting-tunit-tests\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79YGR3Y9RCRS6TD71D0KKP8","dotnet-walls","Walls for a .NET change in a repository without its own quality gates — pinned, ephemeral analyzer, format, clone and scanner commands for the verify step, their identity ratchet, and the build traps. Use during a walls preflight, or when a worker's verify step needs .NET quality gates.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-dotnet-general\u002Fdotnet-walls\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79YGFNJBST7D803NQW3SBYM","csharp-15","Write, review and modernize C# 15 (.NET 11) code correctly. Covers every C# 15 feature - collection expression arguments (`[with(...), ...]`), union types (`union`, `[Union]`, `IUnion`, custom unions), closed class hierarchies (`closed`), extension indexers, labeled `break`\u002F`continue`, non-virtual static interface members on runtimes without default interface methods, and the preview memory-safety model (`unsafe(expr)`, `safe`, requires-unsafe members). Use when code targets net11.0 or LangVersion 15\u002Fpreview, when the user mentions any of these features, when replacing marker interfaces, OneOf-style results, `goto`\u002Fflag loop exits or capacity\u002Fcomparer boilerplate, or when the build reports CS8121, CS8509, CS8655, CS8510, CS0121\u002FCS0411 on a `with(...)` element, CS9370, CS9380 or CS9363.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-dotnet-general\u002Fcsharp-15\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79YGAV031473HSX6FN87ENH","verified-waves","Run one task as verified multi-agent waves. Plans the fan-out, sends findings to fresh skeptics, keeps a ledger, and reports N of M done; small tasks stay solo.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-coordination\u002Fverified-waves\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79YG6QXNND4WRPP3GATSY8J","harness","The bundled dispatch harness, which runs a task file on worker models through OpenCode or Codex, fences their writes, escalates their asks to the operator, settles each result from git and its verify commands, and records every step in a ledger. Its commands, task file, modes and write fence, configuration, runs and their recovery, ledger and exit codes.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-coordination\u002Fharness\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79YG2P5S91SDTA5912XJ4FV","delegating-to-worker-models","Use when you hand off implementation, a plan, research a decision will rely on, or a review, and you brief the worker and check what comes back. A subagent that searches, reads in parallel, or keeps your context small is ordinary tool use. Covers what stays with you, the mechanism, assigning work by strength, the walls preflight, prompts without contradictions, the worker contract and model profiles, evidence from your own run, review, and the fix-up loop.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-coordination\u002Fdelegating-to-worker-models\u002FSKILL.md",[],[]]