[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79Y27QQP7WCD49EM8940TWN":3,"skill-same:01M79Y27QQP7WCD49EM8940TWN":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},"01M79Y27QQP7WCD49EM8940TWN","csharp-refactoring",null,"Safely refactors C#\u002F.NET code without changing behavior. USE FOR any request to refactor, rename, move, extract, inline, merge, consolidate, deduplicate, split, or modernize C# code, even a small extract, inline, or rename, or merging near-identical types; green builds miss drift in #if branches, generated partials, and reflection\u002Fconfig names. When a changed member is visible outside the assembly (PublicAPI.*.txt, InternalsVisibleTo, shipped package), also invoke deniz-dotnet-general:dotnet-breaking-changes; local\u002Fprivate renames do not need it. Also use when a request calls a feature, bug fix, package\u002Fframework upgrade, or public nullability change a refactor and the behavior-changing part must be separated or declined. DO NOT USE FOR ordinary feature or bug fixes not presented as refactoring; standalone upgrades after reclassification; adding tests; or formatting-only work.","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\u002Fplugins\u002Fdeniz-dotnet-general\u002Fskills\u002Fcsharp-refactoring\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: csharp-refactoring\ndescription: \"Safely refactors C#\u002F.NET code without changing behavior. USE FOR\n  any request to refactor, rename, move, extract, inline, merge, consolidate,\n  deduplicate, split, or modernize C# code, even a small extract, inline, or\n  rename, or merging near-identical types; green builds miss drift in #if\n  branches, generated partials, and reflection\u002Fconfig names. When a changed\n  member is visible outside the assembly (PublicAPI.*.txt, InternalsVisibleTo,\n  shipped package), also invoke deniz-dotnet-general:dotnet-breaking-changes; local\u002Fprivate\n  renames do not need it. Also use when a request calls a feature, bug fix,\n  package\u002Fframework upgrade, or public nullability change a refactor and the\n  behavior-changing part must be separated or declined. DO NOT USE FOR ordinary\n  feature or bug fixes not presented as refactoring; standalone upgrades after\n  reclassification; adding tests; or formatting-only work.\"\nlicense: MIT\n---\n\n# C# Refactoring (behavior-preserving)\n\nA refactor changes **structure**, never observable **behavior**. Do the edit with binding-aware tools,\nthen confirm behavior held with a build + the relevant tests. Keep the effort proportional to the change:\na one-line local rename does not need the ceremony a public multi-targeted change does.\n\n## Mandatory gate: classify before validation or editing\n\nRead only enough repository context to classify **each requested operation**. Do this before restoring,\nbuilding, or making an edit. Classification precedence is:\n\n- If the request explicitly asks for at least one separable behavior-preserving operation, complete\n  that structural work and defer only the behavior-changing or contract-changing operations. Do not\n  invent or infer structural work to avoid the whole-request response.\n- If the structural and behavior-changing parts cannot be separated, use the whole-request response\n  and state why they are inseparable.\n- Otherwise, use the whole-request response only when **every** requested operation is outside\n  behavior-preserving refactoring.\n\nFor a whole request that is outside behavior-preserving refactoring:\n\n1. State: `Not a behavior-preserving refactor: \u003Cspecific reason>.`\n2. When the request clearly asks for that work anyway, continue it as ordinary work, outside this\n   skill's no-behavior-change contract, and say so. Otherwise ask once whether to proceed, and change no\n   files until the user answers.\n\n| Requested as a \"refactor\" | Classification and action |\n|---|---|\n| Framework or NuGet version change | **Upgrade.** Do not edit or validate the upgrade as a refactor; it is upgrade work. |\n| New capability, flag, endpoint, tier, or behavior | **Feature.** Do not implement it as a refactor; it is feature work. |\n| Threshold, rate, output, or bug-result change | **Behavior change.** Defer it as bug-fix or behavior-change work; still complete any clearly separable structural operation. |\n| Tighten or loosen a shipped\u002Fpublic nullable annotation | **Source-contract change.** Leave the declaration and API record unchanged; hand off to the `deniz-dotnet-general:dotnet-breaking-changes` skill. |\n\nFor a mixed request, never stop after classification. Perform the separable structural operation,\nexplicitly defer the behavior\u002Fcontract change, and never state `No files changed.` after completing\nstructural work. Never modify tests to make an unauthorized behavior change appear preserved.\n\n## Work only in the current workspace\n\nUse the current agent workspace as the boundary. If it is a Git checkout, resolve its repository root\n(`git rev-parse --show-toplevel`) and stay inside it. If Git metadata is absent, treat the current working\ndirectory and its subdirectories as the boundary, and use a solution or project named in the request\ninside it; Git is not a prerequisite for a refactor. Resolve prompt-provided relative paths inside that\nboundary.\n\nSearch and edit only that workspace. Never use filesystem-wide search or select a similarly named clone,\nanother worktree, build output, or unrelated temporary directory because a file also exists there. If a\nnamed path is absent, stop and report the mismatch instead of guessing another workspace. If a tool rejects\nan in-workspace path for a mechanical reason such as path form or unsupported tool root, retry through\nanother in-workspace mechanism. If the rejection is a permission or policy denial, report it instead of\nworking around it. Never search outside the boundary.\n\n## Rename \u002F move by bindings, not text\n\nThe #1 way a \"rename\" silently corrupts code is editing textual matches (comments, strings, unrelated\noverloads) instead of real **bindings**. Find every binding reference first, then edit semantically. Use\nthe strongest tool available: an IDE\u002FRoslyn workspace refactoring, then a C# language server when the\nharness provides one (`findReferences`, `goToDefinition`, `incomingCalls`, `rename` code action), then analyzer code-fixes \u002F\nRoslynator, then compiler-validated edits (edit the true bindings, rebuild, let the compiler flag misses).\nPlain find\u002Freplace only when scope is provably tiny and every hit is verified. Include **every** `partial`\ndeclaration, and edit the generator input, never generated (`*.g.cs`) output.\n\nFor the operation → Roslyn-provider mapping and representative PRs, see\n[references\u002Foperation-catalog.md](references\u002Foperation-catalog.md).\n\n## Consolidate toward the existing source of truth\n\nWhen de-duplicating, preserve the ownership direction stated by the code or request. If `B` duplicates\nan implementation already owned by `A`, keep `A` canonical and make `B` delegate to it; do not invert\nthe dependency merely because either direction compiles. Preserve public compatibility wrappers when\nthe duplicate surface is shipped, and migrate only in-repo callers that are safe to move.\n\n## Decisions that change the edit\n\nUse the first matching row instead of applying the requested operation mechanically:\n\n| Situation | Do | Never |\n|---|---|---|\n| Inline an internal, unshipped pass-through wrapper | Migrate every binding reference to the target, remove the wrapper, then compile to catch misses. | Keep dead indirection \"for compatibility\" when no compatibility boundary exists. |\n| Inline or remove a shipped\u002Fpublic wrapper | Migrate ordinary in-repo callers, but retain an `[Obsolete]` forwarding entry point unless the request explicitly authorizes a breaking change. | Delete a shipped API merely because all current source callers were migrated. |\n| Rename a member reached by a string, reflection, DI, or configuration | Rename binding-based callers; preserve the observed external name with a forwarding shim or metadata, and exercise the old-name path. | Rewrite an external\u002Fconfigured name just to make the new source name consistent. |\n| Extract duplicated logic whose callers pass different values | Extract the algorithm and pass each caller's existing inputs through unchanged. | Collapse distinct inputs, evaluation order, rounding, or side effects into one caller's version. |\n| Rename code compiled under `#if` or multiple TFMs | Update every source branch and validate each target framework explicitly. | Treat a green default-target build as evidence for unbuilt branches. |\n| Merge near-identical types | Parameterize only the values that differ, migrate every construction site, and preserve each old value exactly. If the old types are internal\u002Funshipped and the request says to merge into one type, delete their declarations. | Retain unnecessary aliases, static holders, factories, or wrapper types that leave the requested merge incomplete; introduce a new hierarchy or behavior. |\n\n## Preserve contracts beyond C# call sites\n\nCompilation proves binding compatibility, not every external contract. Before renaming or moving a\ntype\u002Fmember, check whether its name or metadata is observed by serialization, reflection, dependency\ninjection, configuration binding, source generators, P\u002FInvoke, or `dynamic`.\n\n| Boundary | Required decision |\n|---|---|\n| Serialized\u002Fconfiguration name | Preserve the external name with the repository's existing mechanism (for example, `JsonPropertyName`) while migrating C# callers; run a focused round-trip or payload test. |\n| Public nullable annotation | The mandatory classification gate applies: leave it unchanged and hand off as a source-contract change. |\n| Uncovered reflection or runtime lookup | Do not guess that a compile-clean rename is safe. Preserve the observed name or stop and report the unverified runtime boundary. |\n\n## Verify proportionally\n\nConfirm behavior is preserved after the edit — scaled to blast radius, not a fixed ceremony:\n\n- **Local \u002F private** (method-local or `private` member, one file, single target framework, no public\n  surface, no `partial`\u002Fgenerated\u002F`#if`): skip a separate baseline unless the tree is already suspect.\n  Make the edit, then run the narrowest build and relevant tests once. Let the compiler catch missed\n  references.\n- **Cross-boundary** (public\u002Fshipped symbol, multi-targeted project, `#if`\u002Fplatform branches, or\n  `partial`\u002Fgenerated code): establish a baseline, then run an explicit build and the relevant tests for\n  **each** target framework after the edit (a test command's implicit build is not separate build evidence;\n  a green default build can hide a break on another TFM), and run the hazards check below.\n\nUse the repo's own build\u002Ftest workflow when it documents one (`README`\u002F`CONTRIBUTING`, `build.*`, `eng\u002F`,\n`global.json`, `.github\u002Fworkflows`); its instructions win over any generic command.\n\n### Typical workflow (one operation)\n1. Choose one named refactoring operation and keep the step focused on that operation only.\n2. Find true binding references (`findReferences`\u002F`goToDefinition`\u002Frename) and include all `partial` declarations.\n3. Establish a baseline first only for a cross-boundary change or a tree not already known green.\n4. Apply the change via the most semantics-aware tool available; avoid blind find\u002Freplace when possible.\n5. Rebuild and run the relevant tests. If the gate goes red, report the failure and repair or reassess only\n  your edit; never discard unrelated worktree changes.\n\nWithout a documented repository workflow:\n```bash\ndotnet build   # 0 errors\ndotnet test    # stays green\n```\n\nWhen you took a baseline, the pass count also matches it. One operation per step; never mix a refactor\nand a behavior change in the same step.\n\n## Final response contract\n\nKeep the handoff concise and evidence-based:\n\n- **Refactor:** name the structural operation and the symbols\u002Ffiles changed.\n- **Preserved:** name the behavior or compatibility boundary and the mechanism that preserved it.\n- **Validation:** report the exact commands and observed result; never claim success after a failed restore,\n  build, target framework, or test run.\n- **Deferred:** for a mixed request, name the behavior\u002Fcontract change intentionally left undone and\n  what kind of work it is. Omit this line when nothing was deferred.\n\n## Cross-boundary hazards (only when it touches a boundary)\n\nIf — and only if — the change touches a **public** symbol, an **internal** symbol exposed to a friend\nassembly through `InternalsVisibleTo`, a **multi-targeted** project, or `partial`\u002Fgenerated code, some\nbreaks won't show up as a failing test. Before invoking `deniz-dotnet-general:dotnet-breaking-changes`, apply its scope\nexclusions: skip it for local\u002Fprivate renames and for public-member renames in an executable whose\ncallers all live in that project. Otherwise invoke it before editing; it owns the compatibility\ndecisions, while this skill owns the structural steps. Search the repo for the surface\nthat governs the symbol (don't assume): the public-API gate (`PublicAPI.Shipped\u002FUnshipped.txt` for\nPublicApiAnalyzers, and\u002For `ApiCompat`\u002F`\u003CEnablePackageValidation>` — not interchangeable),\n`\u003CTargetFrameworks>`\u002F`#if` branches, and `InternalsVisibleTo`. Moving a public type to another assembly\nneeds `[TypeForwardedTo]` in the original assembly; a move within one assembly does not. A public\n*rename* needs an `[Obsolete]` shim, not a forwarder. For a provably local\u002Fprivate change, skip these\nchecks.\n\n## Stop an in-scope refactor when\n\n- The baseline is already red (you can't prove you preserved behavior).\n- The requested structural change would alter a public\u002Fshipped API and no compatibility shim or forwarder\n  can preserve it. Report the boundary. Use the gate's handoff format when no structural work was completed;\n  after separable work, put the incompatible operation on the `Deferred:` line instead. Do not ask to make\n  the breaking change.\n- Equivalence depends on runtime behavior tests don't cover (reflection, DI, serialization, `dynamic`,\n  P\u002FInvoke) — report the unverified boundary instead of claiming behavior was preserved.\n","# C# Refactoring (behavior-preserving)\n\nA refactor changes **structure**, never observable **behavior**. Do the edit with binding-aware tools,\nthen confirm behavior held with a build + the relevant tests. Keep the effort proportional to the change:\na one-line local rename does not need the ceremony a public multi-targeted change does.\n\n## Mandatory gate: classify before validation or editing\n\nRead only enough repository context to classify **each requested operation**. Do this before restoring,\nbuilding, or making an edit. Classification precedence is:\n\n- If the request explicitly asks for at least one separable behavior-preserving operation, complete\n  that structural work and defer only the behavior-changing or contract-changing operations. Do not\n  invent or infer structural work to avoid the whole-request response.\n- If the structural and behavior-changing parts cannot be separated, use the whole-request response\n  and state why they are inseparable.\n- Otherwise, use the whole-request response only when **every** requested operation is outside\n  behavior-preserving refactoring.\n\nFor a whole request that is outside behavior-preserving refactoring:\n\n1. State: `Not a behavior-preserving refactor: \u003Cspecific reason>.`\n2. When the request clearly asks for that work anyway, continue it as ordinary work, outside this\n   skill's no-behavior-change contract, and say so. Otherwise ask once whether to proceed, and change no\n   files until the user answers.\n\n| Requested as a \"refactor\" | Classification and action |\n|---|---|\n| Framework or NuGet version change | **Upgrade.** Do not edit or validate the upgrade as a refactor; it is upgrade work. |\n| New capability, flag, endpoint, tier, or behavior | **Feature.** Do not implement it as a refactor; it is feature work. |\n| Threshold, rate, output, or bug-result change | **Behavior change.** Defer it as bug-fix or behavior-change work; still complete any clearly separable structural operation. |\n| Tighten or loosen a shipped\u002Fpublic nullable annotation | **Source-contract change.** Leave the declaration and API record unchanged; hand off to the `deniz-dotnet-general:dotnet-breaking-changes` skill. |\n\nFor a mixed request, never stop after classification. Perform the separable structural operation,\nexplicitly defer the behavior\u002Fcontract change, and never state `No files changed.` after completing\nstructural work. Never modify tests to make an unauthorized behavior change appear preserved.\n\n## Work only in the current workspace\n\nUse the current agent workspace as the boundary. If it is a Git checkout, resolve its repository root\n(`git rev-parse --show-toplevel`) and stay inside it. If Git metadata is absent, treat the current working\ndirectory and its subdirectories as the boundary, and use a solution or project named in the request\ninside it; Git is not a prerequisite for a refactor. Resolve prompt-provided relative paths inside that\nboundary.\n\nSearch and edit only that workspace. Never use filesystem-wide search or select a similarly named clone,\nanother worktree, build output, or unrelated temporary directory because a file also exists there. If a\nnamed path is absent, stop and report the mismatch instead of guessing another workspace. If a tool rejects\nan in-workspace path for a mechanical reason such as path form or unsupported tool root, retry through\nanother in-workspace mechanism. If the rejection is a permission or policy denial, report it instead of\nworking around it. Never search outside the boundary.\n\n## Rename \u002F move by bindings, not text\n\nThe #1 way a \"rename\" silently corrupts code is editing textual matches (comments, strings, unrelated\noverloads) instead of real **bindings**. Find every binding reference first, then edit semantically. Use\nthe strongest tool available: an IDE\u002FRoslyn workspace refactoring, then a C# language server when the\nharness provides one (`findReferences`, `goToDefinition`, `incomingCalls`, `rename` code action), then analyzer code-fixes \u002F\nRoslynator, then compiler-validated edits (edit the true bindings, rebuild, let the compiler flag misses).\nPlain find\u002Freplace only when scope is provably tiny and every hit is verified. Include **every** `partial`\ndeclaration, and edit the generator input, never generated (`*.g.cs`) output.\n\nFor the operation → Roslyn-provider mapping and representative PRs, see\n[references\u002Foperation-catalog.md](references\u002Foperation-catalog.md).\n\n## Consolidate toward the existing source of truth\n\nWhen de-duplicating, preserve the ownership direction stated by the code or request. If `B` duplicates\nan implementation already owned by `A`, keep `A` canonical and make `B` delegate to it; do not invert\nthe dependency merely because either direction compiles. Preserve public compatibility wrappers when\nthe duplicate surface is shipped, and migrate only in-repo callers that are safe to move.\n\n## Decisions that change the edit\n\nUse the first matching row instead of applying the requested operation mechanically:\n\n| Situation | Do | Never |\n|---|---|---|\n| Inline an internal, unshipped pass-through wrapper | Migrate every binding reference to the target, remove the wrapper, then compile to catch misses. | Keep dead indirection \"for compatibility\" when no compatibility boundary exists. |\n| Inline or remove a shipped\u002Fpublic wrapper | Migrate ordinary in-repo callers, but retain an `[Obsolete]` forwarding entry point unless the request explicitly authorizes a breaking change. | Delete a shipped API merely because all current source callers were migrated. |\n| Rename a member reached by a string, reflection, DI, or configuration | Rename binding-based callers; preserve the observed external name with a forwarding shim or metadata, and exercise the old-name path. | Rewrite an external\u002Fconfigured name just to make the new source name consistent. |\n| Extract duplicated logic whose callers pass different values | Extract the algorithm and pass each caller's existing inputs through unchanged. | Collapse distinct inputs, evaluation order, rounding, or side effects into one caller's version. |\n| Rename code compiled under `#if` or multiple TFMs | Update every source branch and validate each target framework explicitly. | Treat a green default-target build as evidence for unbuilt branches. |\n| Merge near-identical types | Parameterize only the values that differ, migrate every construction site, and preserve each old value exactly. If the old types are internal\u002Funshipped and the request says to merge into one type, delete their declarations. | Retain unnecessary aliases, static holders, factories, or wrapper types that leave the requested merge incomplete; introduce a new hierarchy or behavior. |\n\n## Preserve contracts beyond C# call sites\n\nCompilation proves binding compatibility, not every external contract. Before renaming or moving a\ntype\u002Fmember, check whether its name or metadata is observed by serialization, reflection, dependency\ninjection, configuration binding, source generators, P\u002FInvoke, or `dynamic`.\n\n| Boundary | Required decision |\n|---|---|\n| Serialized\u002Fconfiguration name | Preserve the external name with the repository's existing mechanism (for example, `JsonPropertyName`) while migrating C# callers; run a focused round-trip or payload test. |\n| Public nullable annotation | The mandatory classification gate applies: leave it unchanged and hand off as a source-contract change. |\n| Uncovered reflection or runtime lookup | Do not guess that a compile-clean rename is safe. Preserve the observed name or stop and report the unverified runtime boundary. |\n\n## Verify proportionally\n\nConfirm behavior is preserved after the edit — scaled to blast radius, not a fixed ceremony:\n\n- **Local \u002F private** (method-local or `private` member, one file, single target framework, no public\n  surface, no `partial`\u002Fgenerated\u002F`#if`): skip a separate baseline unless the tree is already suspect.\n  Make the edit, then run the narrowest build and relevant tests once. Let the compiler catch missed\n  references.\n- **Cross-boundary** (public\u002Fshipped symbol, multi-targeted project, `#if`\u002Fplatform branches, or\n  `partial`\u002Fgenerated code): establish a baseline, then run an explicit build and the relevant tests for\n  **each** target framework after the edit (a test command's implicit build is not separate build evidence;\n  a green default build can hide a break on another TFM), and run the hazards check below.\n\nUse the repo's own build\u002Ftest workflow when it documents one (`README`\u002F`CONTRIBUTING`, `build.*`, `eng\u002F`,\n`global.json`, `.github\u002Fworkflows`); its instructions win over any generic command.\n\n### Typical workflow (one operation)\n1. Choose one named refactoring operation and keep the step focused on that operation only.\n2. Find true binding references (`findReferences`\u002F`goToDefinition`\u002Frename) and include all `partial` declarations.\n3. Establish a baseline first only for a cross-boundary change or a tree not already known green.\n4. Apply the change via the most semantics-aware tool available; avoid blind find\u002Freplace when possible.\n5. Rebuild and run the relevant tests. If the gate goes red, report the failure and repair or reassess only\n  your edit; never discard unrelated worktree changes.\n\nWithout a documented repository workflow:\n```bash\ndotnet build   # 0 errors\ndotnet test    # stays green\n```\n\nWhen you took a baseline, the pass count also matches it. One operation per step; never mix a refactor\nand a behavior change in the same step.\n\n## Final response contract\n\nKeep the handoff concise and evidence-based:\n\n- **Refactor:** name the structural operation and the symbols\u002Ffiles changed.\n- **Preserved:** name the behavior or compatibility boundary and the mechanism that preserved it.\n- **Validation:** report the exact commands and observed result; never claim success after a failed restore,\n  build, target framework, or test run.\n- **Deferred:** for a mixed request, name the behavior\u002Fcontract change intentionally left undone and\n  what kind of work it is. Omit this line when nothing was deferred.\n\n## Cross-boundary hazards (only when it touches a boundary)\n\nIf — and only if — the change touches a **public** symbol, an **internal** symbol exposed to a friend\nassembly through `InternalsVisibleTo`, a **multi-targeted** project, or `partial`\u002Fgenerated code, some\nbreaks won't show up as a failing test. Before invoking `deniz-dotnet-general:dotnet-breaking-changes`, apply its scope\nexclusions: skip it for local\u002Fprivate renames and for public-member renames in an executable whose\ncallers all live in that project. Otherwise invoke it before editing; it owns the compatibility\ndecisions, while this skill owns the structural steps. Search the repo for the surface\nthat governs the symbol (don't assume): the public-API gate (`PublicAPI.Shipped\u002FUnshipped.txt` for\nPublicApiAnalyzers, and\u002For `ApiCompat`\u002F`\u003CEnablePackageValidation>` — not interchangeable),\n`\u003CTargetFrameworks>`\u002F`#if` branches, and `InternalsVisibleTo`. Moving a public type to another assembly\nneeds `[TypeForwardedTo]` in the original assembly; a move within one assembly does not. A public\n*rename* needs an `[Obsolete]` shim, not a forwarder. For a provably local\u002Fprivate change, skip these\nchecks.\n\n## Stop an in-scope refactor when\n\n- The baseline is already red (you can't prove you preserved behavior).\n- The requested structural change would alter a public\u002Fshipped API and no compatibility shim or forwarder\n  can preserve it. Report the boundary. Use the gate's handoff format when no structural work was completed;\n  after separable work, put the incompatible operation on the `Deferred:` line instead. Do not ask to make\n  the breaking change.\n- Equivalence depends on runtime behavior tests don't cover (reflection, DI, serialization, `dynamic`,\n  P\u002FInvoke) — report the unverified boundary instead of claiming behavior was preserved.\n",{"name":5,"license":15,"description":7},"master","b30b1c1908dbc56a8184128f18803053d762ccb5","plugins\u002Fdeniz-dotnet-general\u002Fskills\u002Fcsharp-refactoring",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 csharp-refactoring",{"tool":39,"command":40},"bunx","bunx skills add Blind-Striker\u002Fagent-skills-and-plugins --skill csharp-refactoring",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Blind-Striker\u002Fagent-skills-and-plugins --skill csharp-refactoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fplugins\u002Fdeniz-dotnet-general\u002Fskills\u002Fcsharp-refactoring\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Foperation-catalog.md","REFERENCE","参考文档",3186,"https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fplugins\u002Fdeniz-dotnet-general\u002Fskills\u002Fcsharp-refactoring\u002Freferences\u002Foperation-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",[],[]]