[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79X97T1VVCKPATGF64E9Y63":3,"skill-same:01M79X97T1VVCKPATGF64E9Y63":79},{"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},"01M79X97T1VVCKPATGF64E9Y63","deniz-dotnet-general.coverage-analysis",null,"Analyzes .NET Cobertura line, branch, and condition evidence. Activation requires supplied .NET coverage evidence (a report, percentages, or line, branch, or condition metrics), an explicit request to collect .NET coverage for analysis, or an explicit CRAP request. Use for coverage plateaus, target arithmetic, project-wide CRAP\u002Frefactoring-risk hotspots, or a targeted CRAP calculation on one exact method, class, or source file. A supplied report is analyzed directly without rerunning tests, installing tools, or generating reports. Project-wide requests rank complex, under-covered members; targeted requests filter existing method rows and report only the requested scope. DO NOT USE FOR: requests with none of that evidence or intent, including hypothetical change-survival questions; behavioral\u002Fpseudo-mutation gaps, test-code audits, writing tests, or running tests without coverage context.","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.coverage-analysis\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: deniz-dotnet-general.coverage-analysis\ndescription: >\n  Analyzes .NET Cobertura line, branch, and condition evidence. Activation\n  requires supplied .NET coverage evidence (a report, percentages, or line,\n  branch, or condition metrics), an explicit request to collect .NET coverage\n  for analysis, or an explicit CRAP request. Use for coverage plateaus, target\n  arithmetic, project-wide CRAP\u002Frefactoring-risk hotspots, or a targeted CRAP\n  calculation on one exact method, class, or source file. A supplied report is\n  analyzed directly without rerunning tests, installing tools, or generating\n  reports. Project-wide requests rank complex, under-covered members; targeted\n  requests filter existing method rows and report only the requested scope. DO\n  NOT USE FOR: requests with none of that evidence or intent, including\n  hypothetical change-survival questions; behavioral\u002Fpseudo-mutation gaps,\n  test-code audits, writing tests, or running tests without coverage context.\n---\n\n# Coverage Analysis\n\n## Purpose\n\nExplain what .NET coverage evidence proves, reconcile target arithmetic, and\nidentify the code blocking progress. Add complexity\u002FCRAP ranking only when the\nuser explicitly asks for risk hotspots, CRAP, priorities by risk, or refactoring\nsafety.\n\n## When to Use\n\nUse this skill for interpreting supplied .NET line\u002Fbranch\u002Fcondition evidence,\ncoverage gaps and plateaus, target arithmetic, or explicit project-wide\ncoverage-backed risk analysis.\n\n## When Not to Use\n\n- **Behavioral or pseudo-mutation gaps in existing tests** — use `test-gap-analysis`\n- **Writing or generating tests** — this skill identifies where tests are needed, not write them\n- **General test execution** unrelated to coverage or CRAP analysis\n- **Only collecting .NET coverage or printing a raw percentage with no diagnosis** — use `run-tests`; use native tooling for non-.NET coverage collection or analysis. Interpreting .NET line\u002Fbranch gaps remains in scope here\n\n## Inputs\n\n| Input | Required | Default | Description |\n|-------|----------|---------|-------------|\n| Target scope | No | None | Exact method name, class name, or source-file path; selects the targeted CRAP path |\n| Project\u002Fsolution path | No | Current directory | Path to the .NET solution or project |\n| Line coverage threshold | No | 80% | Minimum acceptable line coverage |\n| Branch coverage threshold | No | 70% | Minimum acceptable branch coverage |\n| Existing Cobertura path | No | Discover only if not supplied | Preferred input; never rerun tests when usable |\n| CRAP threshold | No | 30 | Used only for explicit risk\u002FCRAP requests |\n| Hotspot count | No | 3 | Explicit risk requests only; cap at 10 unless the user asks for more |\n\nDiscover optional inputs from the workspace. Do not ask for a project path when\nthe current directory or a supplied report is sufficient.\n\n## Choose the smallest matching path\n\n| User intent | Required work | Do not do |\n|-------------|---------------|-----------|\n| Explain a supplied excerpt, condition, or summary | Answer directly from the supplied evidence | Tools, CRAP, discovery, report files |\n| Interpret a supplied Cobertura path or diagnose a plateau | Read that report, reconcile totals, name all material gaps, answer directly | Rerun tests, install tools, compute CRAP, or generate files unless explicitly requested |\n| Compute CRAP for one exact method, class, or file | Resolve the Cobertura rows for that target and compute CRAP only for those rows | Project-wide hotspot ranking or report generation |\n| Rank risk hotspots, compute project-wide CRAP, or assess refactoring safety | Use the supplied\u002Fexisting report, read `references\u002Fguidelines.md`, and compute CRAP before ranking | Coverage-only ranking or a full report template unless requested |\n| Analyze coverage when no report exists | Invoke `deniz-dotnet-general.run-tests` to collect Cobertura coverage with the repository-compatible runner, then analyze the generated report | Choose or execute a test command independently; CRAP unless risk was requested |\n| Produce a full markdown\u002FHTML\u002FCSV report | First deliver the direct answer; then read `references\u002Foutput-format.md` or `references\u002Freport-generation.md` | Report generation before the answer |\n\nWords such as **analyze coverage**, **what is blocking coverage**, or **why is\ncoverage stuck** do not by themselves request CRAP. Explicit signals include\n**risk hotspot**, **CRAP**, **complexity-weighted priority**, **safe to refactor**,\nor an equivalent request to combine complexity with coverage.\n\n### Targeted CRAP path\n\nWhen the user names one exact method, class, or source file, use supplied or\nexisting Cobertura data when available; otherwise follow the normal collection\npath once. Then run\n`pwsh -File scripts\u002FExtract-MethodCoverage.ps1 -CoberturaPath \u003Creport> -Filter all -OutputFormat json-v1`\nand read its exit code beside the JSON:\n\n- **Exit 2:** the input is invalid or contradictory, such as a non-Cobertura\n  root, covered counts above valid counts, or duplicate method identities. That\n  is failed collection, not 0% coverage: regenerate coverage when possible,\n  otherwise stop without publishing a CRAP score.\n- **Exit 3:** the evidence is partial. Continue, and score only the rows whose\n  measurements are exact.\n- **Exit 0:** every measurement is exact.\n\nFilter `data.methods` for a method target by exact `Class` plus exact `Method`,\nand by exact `Signature` too when the user gives one; for a class target by\nexact `Class`; for a file target by normalized `File` path (the script writes\n`\u002F` separators). When a method target still matches more than one row, such as\noverloads, report the ambiguity and the matching rows rather than widening the\nselection. A report with no method rows, or no row that matches, is failed\ncollection or filtering, not 0% coverage: report that the target is absent from\nthe Cobertura data and do not invent a score.\n\nA matching row with `ComplexityStatus: unknown` has a null `Complexity`: its\nCobertura method had no `complexity` attribute, or the merged reports disagree.\nCount that method's decision points in the current source only when that source\nis the revision the report was collected from, such as a report you just\ncollected from the unchanged checkout, and label the result a manual count. The\nscripts record no source revision, so for any other report mark its CRAP score\nunavailable rather than mix current complexity with old coverage. A row with\n`LineCoverageStatus: unknown` has no line evidence, so its CRAP score is\nunavailable. For each matching row with an exact or counted complexity and exact\nline coverage, calculate:\n\n```text\nCRAP(m) = complexity^2 * (1 - lineCoverage)^3 + complexity\n```\n\nHere `lineCoverage` is the fraction `CoveredLines \u002F TotalLines` from the row, as\nthe shipped scorer computes it; the rounded `LineCoverage` percentage can shift\nthe score.\n\nReport only the selected rows, the formula inputs, the resulting score, and one\nconcrete coverage or complexity recommendation. Do not emit the project-wide\nhotspot inventory or optional reports unless the user separately requests them.\n\n## Existing-data fast path\n\nWhen the user supplies a coverage excerpt, summary, or valid Cobertura path:\n\n- Treat it as authoritative input and start there.\n- Do not discover the solution or test projects unless source mapping is necessary.\n- Do not run `dotnet test`, install ReportGenerator, add a coverage package, or\n  read `references\u002Fsetup-discovery.md` or `references\u002Freport-generation.md`.\n- Do not write `coverage-analysis.md` or create a report directory unless the user\n  requested a saved\u002Ffull report.\n- For interpretation and plateau questions, parse only the evidence needed to\n  answer. For explicit project-wide risk requests, use the bundled scripts as\n  described in `references\u002Fguidelines.md`.\n\nA failed read\u002Fview operation is not proof that a named path does not exist.\nClassify the failure, then make one targeted existence probe and use a normalized\npath or alternate reader only for confirmed tool availability, transport, or\npath-normalization failures and only after verifying the canonical path remains\ninside the workspace. Stop on content-exclusion, permission\u002Fpolicy,\nworkspace-boundary, or unknown failures. Report a missing path only when the\nindependent probe also fails; do not broaden the search or substitute another\nartifact.\n\n## Collection path\n\nUse this path only when no usable coverage evidence exists and the user asked for\nanalysis that requires it.\n\n1. Read `references\u002Fsetup-discovery.md`.\n2. Prefer existing Cobertura discovered under the requested root.\n3. If none exists, invoke `deniz-dotnet-general.run-tests` for repository overlay, platform,\n   runner, and command selection, and have it collect Cobertura once per entry point.\n4. Analyze the resulting Cobertura. Compute CRAP only if risk analysis was\n   explicitly requested.\n\nWhen the workspace contains the project\u002Ftest manifests needed by this path,\nperform discovery directly and delegate collection to `deniz-dotnet-general.run-tests`. Do not ask\nthe user to attach files or pre-run coverage that the current workspace lets\nyou inspect and generate.\n\nDo not modify production code. Do not add coverage packages, change project\nmanifests, or install global tools unless the user explicitly authorized\ndependency or tooling changes. If the repository lacks a usable coverage\nprovider, report that exact prerequisite and the compatible command shape that\n`deniz-dotnet-general.run-tests` identified, then stop.\n\nThe automatic collection path is for SDK-style projects. For classic non-SDK or\n`packages.config` projects, use only a repository-owned coverage command. If none\nexists, stop and request Cobertura XML. Never migrate the project, inject an\nSDK-style provider, create a wrapper project, or report substitute coverage from\nanother assembly.\n\n## Interpretation and arithmetic invariants\n\n- A line hit proves execution, not both decision outcomes.\n- `condition-coverage=\"50% (1\u002F2)\"` proves one reported outcome ran, but not which\n  one. Recommend forcing the opposite outcome. Without source, never invent likely\n  predicates or claim whether true or false is missing. State that compound\n  predicates need independently exercised operands and short-circuit combinations\n  when applicable; do not infer the exact combinations without source or fuller XML.\n- Derive overall totals from Cobertura's covered\u002Fvalid line counts. For target\n  `T`, required covered lines are `ceiling(valid lines × T)`.\n- Projected coverage is `(current covered lines + newly covered distinct lines) \u002F\n  valid lines`. State assumptions such as fully covering a method.\n- When asked whether one member can reach a target, show its maximum projected\n  total and at least one concrete sufficient combination of supplied members or\n  line gains. If no supplied combination is sufficient, say so.\n- For a multi-member target, name the exact combination and resulting covered \u002F\n  valid total; saying only \"combine it with another member\" is incomplete.\n- Reconcile member gaps against project totals. Method line ranges can overlap or\n  omit class-level lines, so do not sum method counts as project truth.\n- Never call one member the **sole**, **entire**, or **all** remaining gap unless\n  its distinct uncovered lines exactly reconcile with the project total and no\n  other below-threshold member remains.\n- Name every supplied or extracted below-threshold member, but keep detail\n  proportional: lead with the blockers, summarize the remainder in one sentence\n  or a compact table.\n\n## Response contract\n\nAnswer the user's question in the first 2–4 sentences.\n\n- **Excerpt or arithmetic question:** one explanation plus the next test or member\n  priority. No dashboard.\n- **Existing-report interpretation or plateau:** overall line\u002Fbranch coverage,\n  blocking members, reconciled target impact, and 1–3 recommendations. Use at\n  most one compact table.\n- **Explicit risk\u002FCRAP request:** top 3 actual hotspots by default, supporting\n  complexity\u002Fcoverage\u002FCRAP values, remaining flagged count, and 1–3 priorities.\n  Exclude fully covered low-risk methods from the hotspot table. Never exceed 10\n  rows unless the user requests a larger count. For refactoring safety, rank risky\n  methods by CRAP rather than raw coverage alone, then name comparatively safe\n  well-covered methods separately.\n- **Explicit full report request:** read `references\u002Foutput-format.md`. Save the\n  report only then.\n\nReport only artifacts that exist. Do not announce inaccessible output paths or\nfailed optional file writes when no file was requested.\n\n## Optional reports\n\nHTML\u002FCSV\u002Fmarkdown files are not part of normal analysis. Generate them only when\nthe user explicitly requests report files or a CI artifact.\n\n1. Deliver the direct coverage\u002Frisk answer first.\n2. For a full markdown report, read `references\u002Foutput-format.md` and save it.\n3. For HTML\u002FCSV, then read `references\u002Freport-generation.md`. Do not install\n   ReportGenerator before the direct answer, and do not retry a failed install.\n\n## Validation\n\n- Confirm a supplied report was used without test execution or tool installation.\n- Reconcile covered, valid, and uncovered line totals before projecting impact.\n- Confirm every stated blocker comes from supplied or extracted evidence.\n- If CRAP was requested, spot-check one score using `references\u002Fguidelines.md`.\n- If files were requested, verify they exist before reporting their paths.\n\n## Common Pitfalls\n\n- **Existing report triggers setup work** — stop. Analyze the named artifact first.\n- **Generic analysis triggers CRAP** — stop. CRAP requires explicit risk intent.\n- **One method is called the entire gap** — reconcile distinct uncovered lines and\n  the full below-threshold set first.\n- **A small request gets a dashboard** — scale down to a direct answer or one table.\n- **No Cobertura from collection** — report the collection failure; do not invent\n  substitute coverage.\n- **Compiler-generated method names** — verify suspicious async, lambda, or local\n  function names against source before presenting them as user-authored members.\n- **Test exit code 1** — coverage may still exist; proceed with a warning. Other\n  nonzero build failures stop the collection path.\n","# Coverage Analysis\n\n## Purpose\n\nExplain what .NET coverage evidence proves, reconcile target arithmetic, and\nidentify the code blocking progress. Add complexity\u002FCRAP ranking only when the\nuser explicitly asks for risk hotspots, CRAP, priorities by risk, or refactoring\nsafety.\n\n## When to Use\n\nUse this skill for interpreting supplied .NET line\u002Fbranch\u002Fcondition evidence,\ncoverage gaps and plateaus, target arithmetic, or explicit project-wide\ncoverage-backed risk analysis.\n\n## When Not to Use\n\n- **Behavioral or pseudo-mutation gaps in existing tests** — use `test-gap-analysis`\n- **Writing or generating tests** — this skill identifies where tests are needed, not write them\n- **General test execution** unrelated to coverage or CRAP analysis\n- **Only collecting .NET coverage or printing a raw percentage with no diagnosis** — use `run-tests`; use native tooling for non-.NET coverage collection or analysis. Interpreting .NET line\u002Fbranch gaps remains in scope here\n\n## Inputs\n\n| Input | Required | Default | Description |\n|-------|----------|---------|-------------|\n| Target scope | No | None | Exact method name, class name, or source-file path; selects the targeted CRAP path |\n| Project\u002Fsolution path | No | Current directory | Path to the .NET solution or project |\n| Line coverage threshold | No | 80% | Minimum acceptable line coverage |\n| Branch coverage threshold | No | 70% | Minimum acceptable branch coverage |\n| Existing Cobertura path | No | Discover only if not supplied | Preferred input; never rerun tests when usable |\n| CRAP threshold | No | 30 | Used only for explicit risk\u002FCRAP requests |\n| Hotspot count | No | 3 | Explicit risk requests only; cap at 10 unless the user asks for more |\n\nDiscover optional inputs from the workspace. Do not ask for a project path when\nthe current directory or a supplied report is sufficient.\n\n## Choose the smallest matching path\n\n| User intent | Required work | Do not do |\n|-------------|---------------|-----------|\n| Explain a supplied excerpt, condition, or summary | Answer directly from the supplied evidence | Tools, CRAP, discovery, report files |\n| Interpret a supplied Cobertura path or diagnose a plateau | Read that report, reconcile totals, name all material gaps, answer directly | Rerun tests, install tools, compute CRAP, or generate files unless explicitly requested |\n| Compute CRAP for one exact method, class, or file | Resolve the Cobertura rows for that target and compute CRAP only for those rows | Project-wide hotspot ranking or report generation |\n| Rank risk hotspots, compute project-wide CRAP, or assess refactoring safety | Use the supplied\u002Fexisting report, read `references\u002Fguidelines.md`, and compute CRAP before ranking | Coverage-only ranking or a full report template unless requested |\n| Analyze coverage when no report exists | Invoke `deniz-dotnet-general.run-tests` to collect Cobertura coverage with the repository-compatible runner, then analyze the generated report | Choose or execute a test command independently; CRAP unless risk was requested |\n| Produce a full markdown\u002FHTML\u002FCSV report | First deliver the direct answer; then read `references\u002Foutput-format.md` or `references\u002Freport-generation.md` | Report generation before the answer |\n\nWords such as **analyze coverage**, **what is blocking coverage**, or **why is\ncoverage stuck** do not by themselves request CRAP. Explicit signals include\n**risk hotspot**, **CRAP**, **complexity-weighted priority**, **safe to refactor**,\nor an equivalent request to combine complexity with coverage.\n\n### Targeted CRAP path\n\nWhen the user names one exact method, class, or source file, use supplied or\nexisting Cobertura data when available; otherwise follow the normal collection\npath once. Then run\n`pwsh -File scripts\u002FExtract-MethodCoverage.ps1 -CoberturaPath \u003Creport> -Filter all -OutputFormat json-v1`\nand read its exit code beside the JSON:\n\n- **Exit 2:** the input is invalid or contradictory, such as a non-Cobertura\n  root, covered counts above valid counts, or duplicate method identities. That\n  is failed collection, not 0% coverage: regenerate coverage when possible,\n  otherwise stop without publishing a CRAP score.\n- **Exit 3:** the evidence is partial. Continue, and score only the rows whose\n  measurements are exact.\n- **Exit 0:** every measurement is exact.\n\nFilter `data.methods` for a method target by exact `Class` plus exact `Method`,\nand by exact `Signature` too when the user gives one; for a class target by\nexact `Class`; for a file target by normalized `File` path (the script writes\n`\u002F` separators). When a method target still matches more than one row, such as\noverloads, report the ambiguity and the matching rows rather than widening the\nselection. A report with no method rows, or no row that matches, is failed\ncollection or filtering, not 0% coverage: report that the target is absent from\nthe Cobertura data and do not invent a score.\n\nA matching row with `ComplexityStatus: unknown` has a null `Complexity`: its\nCobertura method had no `complexity` attribute, or the merged reports disagree.\nCount that method's decision points in the current source only when that source\nis the revision the report was collected from, such as a report you just\ncollected from the unchanged checkout, and label the result a manual count. The\nscripts record no source revision, so for any other report mark its CRAP score\nunavailable rather than mix current complexity with old coverage. A row with\n`LineCoverageStatus: unknown` has no line evidence, so its CRAP score is\nunavailable. For each matching row with an exact or counted complexity and exact\nline coverage, calculate:\n\n```text\nCRAP(m) = complexity^2 * (1 - lineCoverage)^3 + complexity\n```\n\nHere `lineCoverage` is the fraction `CoveredLines \u002F TotalLines` from the row, as\nthe shipped scorer computes it; the rounded `LineCoverage` percentage can shift\nthe score.\n\nReport only the selected rows, the formula inputs, the resulting score, and one\nconcrete coverage or complexity recommendation. Do not emit the project-wide\nhotspot inventory or optional reports unless the user separately requests them.\n\n## Existing-data fast path\n\nWhen the user supplies a coverage excerpt, summary, or valid Cobertura path:\n\n- Treat it as authoritative input and start there.\n- Do not discover the solution or test projects unless source mapping is necessary.\n- Do not run `dotnet test`, install ReportGenerator, add a coverage package, or\n  read `references\u002Fsetup-discovery.md` or `references\u002Freport-generation.md`.\n- Do not write `coverage-analysis.md` or create a report directory unless the user\n  requested a saved\u002Ffull report.\n- For interpretation and plateau questions, parse only the evidence needed to\n  answer. For explicit project-wide risk requests, use the bundled scripts as\n  described in `references\u002Fguidelines.md`.\n\nA failed read\u002Fview operation is not proof that a named path does not exist.\nClassify the failure, then make one targeted existence probe and use a normalized\npath or alternate reader only for confirmed tool availability, transport, or\npath-normalization failures and only after verifying the canonical path remains\ninside the workspace. Stop on content-exclusion, permission\u002Fpolicy,\nworkspace-boundary, or unknown failures. Report a missing path only when the\nindependent probe also fails; do not broaden the search or substitute another\nartifact.\n\n## Collection path\n\nUse this path only when no usable coverage evidence exists and the user asked for\nanalysis that requires it.\n\n1. Read `references\u002Fsetup-discovery.md`.\n2. Prefer existing Cobertura discovered under the requested root.\n3. If none exists, invoke `deniz-dotnet-general.run-tests` for repository overlay, platform,\n   runner, and command selection, and have it collect Cobertura once per entry point.\n4. Analyze the resulting Cobertura. Compute CRAP only if risk analysis was\n   explicitly requested.\n\nWhen the workspace contains the project\u002Ftest manifests needed by this path,\nperform discovery directly and delegate collection to `deniz-dotnet-general.run-tests`. Do not ask\nthe user to attach files or pre-run coverage that the current workspace lets\nyou inspect and generate.\n\nDo not modify production code. Do not add coverage packages, change project\nmanifests, or install global tools unless the user explicitly authorized\ndependency or tooling changes. If the repository lacks a usable coverage\nprovider, report that exact prerequisite and the compatible command shape that\n`deniz-dotnet-general.run-tests` identified, then stop.\n\nThe automatic collection path is for SDK-style projects. For classic non-SDK or\n`packages.config` projects, use only a repository-owned coverage command. If none\nexists, stop and request Cobertura XML. Never migrate the project, inject an\nSDK-style provider, create a wrapper project, or report substitute coverage from\nanother assembly.\n\n## Interpretation and arithmetic invariants\n\n- A line hit proves execution, not both decision outcomes.\n- `condition-coverage=\"50% (1\u002F2)\"` proves one reported outcome ran, but not which\n  one. Recommend forcing the opposite outcome. Without source, never invent likely\n  predicates or claim whether true or false is missing. State that compound\n  predicates need independently exercised operands and short-circuit combinations\n  when applicable; do not infer the exact combinations without source or fuller XML.\n- Derive overall totals from Cobertura's covered\u002Fvalid line counts. For target\n  `T`, required covered lines are `ceiling(valid lines × T)`.\n- Projected coverage is `(current covered lines + newly covered distinct lines) \u002F\n  valid lines`. State assumptions such as fully covering a method.\n- When asked whether one member can reach a target, show its maximum projected\n  total and at least one concrete sufficient combination of supplied members or\n  line gains. If no supplied combination is sufficient, say so.\n- For a multi-member target, name the exact combination and resulting covered \u002F\n  valid total; saying only \"combine it with another member\" is incomplete.\n- Reconcile member gaps against project totals. Method line ranges can overlap or\n  omit class-level lines, so do not sum method counts as project truth.\n- Never call one member the **sole**, **entire**, or **all** remaining gap unless\n  its distinct uncovered lines exactly reconcile with the project total and no\n  other below-threshold member remains.\n- Name every supplied or extracted below-threshold member, but keep detail\n  proportional: lead with the blockers, summarize the remainder in one sentence\n  or a compact table.\n\n## Response contract\n\nAnswer the user's question in the first 2–4 sentences.\n\n- **Excerpt or arithmetic question:** one explanation plus the next test or member\n  priority. No dashboard.\n- **Existing-report interpretation or plateau:** overall line\u002Fbranch coverage,\n  blocking members, reconciled target impact, and 1–3 recommendations. Use at\n  most one compact table.\n- **Explicit risk\u002FCRAP request:** top 3 actual hotspots by default, supporting\n  complexity\u002Fcoverage\u002FCRAP values, remaining flagged count, and 1–3 priorities.\n  Exclude fully covered low-risk methods from the hotspot table. Never exceed 10\n  rows unless the user requests a larger count. For refactoring safety, rank risky\n  methods by CRAP rather than raw coverage alone, then name comparatively safe\n  well-covered methods separately.\n- **Explicit full report request:** read `references\u002Foutput-format.md`. Save the\n  report only then.\n\nReport only artifacts that exist. Do not announce inaccessible output paths or\nfailed optional file writes when no file was requested.\n\n## Optional reports\n\nHTML\u002FCSV\u002Fmarkdown files are not part of normal analysis. Generate them only when\nthe user explicitly requests report files or a CI artifact.\n\n1. Deliver the direct coverage\u002Frisk answer first.\n2. For a full markdown report, read `references\u002Foutput-format.md` and save it.\n3. For HTML\u002FCSV, then read `references\u002Freport-generation.md`. Do not install\n   ReportGenerator before the direct answer, and do not retry a failed install.\n\n## Validation\n\n- Confirm a supplied report was used without test execution or tool installation.\n- Reconcile covered, valid, and uncovered line totals before projecting impact.\n- Confirm every stated blocker comes from supplied or extracted evidence.\n- If CRAP was requested, spot-check one score using `references\u002Fguidelines.md`.\n- If files were requested, verify they exist before reporting their paths.\n\n## Common Pitfalls\n\n- **Existing report triggers setup work** — stop. Analyze the named artifact first.\n- **Generic analysis triggers CRAP** — stop. CRAP requires explicit risk intent.\n- **One method is called the entire gap** — reconcile distinct uncovered lines and\n  the full below-threshold set first.\n- **A small request gets a dashboard** — scale down to a direct answer or one table.\n- **No Cobertura from collection** — report the collection failure; do not invent\n  substitute coverage.\n- **Compiler-generated method names** — verify suspicious async, lambda, or local\n  function names against source before presenting them as user-authored members.\n- **Test exit code 1** — coverage may still exist; proceed with a warning. Other\n  nonzero build failures stop the collection path.\n",{"name":5,"description":7},"master","b30b1c1908dbc56a8184128f18803053d762ccb5","opencode\u002Fdeniz-dotnet-general\u002Fskills\u002Fdeniz-dotnet-general.coverage-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.coverage-analysis",{"tool":39,"command":40},"bunx","bunx skills add Blind-Striker\u002Fagent-skills-and-plugins --skill deniz-dotnet-general.coverage-analysis",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Blind-Striker\u002Fagent-skills-and-plugins --skill deniz-dotnet-general.coverage-analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fopencode\u002Fdeniz-dotnet-general\u002Fskills\u002Fdeniz-dotnet-general.coverage-analysis\u002FSKILL.md",true,[47,53,57,61,65,71,75],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fguidelines.md","REFERENCE","参考文档",3549,"https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fopencode\u002Fdeniz-dotnet-general\u002Fskills\u002Fdeniz-dotnet-general.coverage-analysis\u002Freferences\u002Fguidelines.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Foutput-format.md",4220,"https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fopencode\u002Fdeniz-dotnet-general\u002Fskills\u002Fdeniz-dotnet-general.coverage-analysis\u002Freferences\u002Foutput-format.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Freport-generation.md",2089,"https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fopencode\u002Fdeniz-dotnet-general\u002Fskills\u002Fdeniz-dotnet-general.coverage-analysis\u002Freferences\u002Freport-generation.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fsetup-discovery.md",15392,"https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fopencode\u002Fdeniz-dotnet-general\u002Fskills\u002Fdeniz-dotnet-general.coverage-analysis\u002Freferences\u002Fsetup-discovery.md",{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"scripts\u002FCompute-CrapScores.ps1","SCRIPT","脚本",4451,"https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fopencode\u002Fdeniz-dotnet-general\u002Fskills\u002Fdeniz-dotnet-general.coverage-analysis\u002Fscripts\u002FCompute-CrapScores.ps1",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"scripts\u002FCoverageData.ps1",14719,"https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fopencode\u002Fdeniz-dotnet-general\u002Fskills\u002Fdeniz-dotnet-general.coverage-analysis\u002Fscripts\u002FCoverageData.ps1",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002FExtract-MethodCoverage.ps1",3636,"https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fopencode\u002Fdeniz-dotnet-general\u002Fskills\u002Fdeniz-dotnet-general.coverage-analysis\u002Fscripts\u002FExtract-MethodCoverage.ps1",[80,87,94,101,108,115],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"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",[],[]]