[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79WSFYK5195F7RKFE1RBV2V":3,"skill-same:01M79WSFYK5195F7RKFE1RBV2V":47},{"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},"01M79WSFYK5195F7RKFE1RBV2V","find-repeated-work-within-one-build",null,"Use ONLY for auditing executed-task counts or batching\u002Fhoisting costs within ONE MSBuild invocation: per-project Exec, duplicate dependency builds, per-item generators, run-once races. NEVER load for evaluation-only global-property variants with once-only target\u002Ftask execution, idle-node\u002Fserial-chain investigations, second\u002Funchanged builds, restores across commands, required-variant bin\u002Fobj collisions or unranked slowness. Do not load to check scope or replace an unavailable specialist; answer directly.","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\u002Fcodex\u002Fdeniz-dotnet-general\u002Fskills\u002Ffind-repeated-work-within-one-build\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: find-repeated-work-within-one-build\ndescription: \"Use ONLY for auditing executed-task counts or batching\u002Fhoisting\n  costs within ONE MSBuild invocation: per-project Exec, duplicate dependency\n  builds, per-item generators, run-once races. NEVER load for evaluation-only\n  global-property variants with once-only target\u002Ftask execution,\n  idle-node\u002Fserial-chain investigations, second\u002Funchanged builds, restores\n  across commands, required-variant bin\u002Fobj collisions or unranked slowness. Do\n  not load to check scope or replace an unavailable specialist; answer\n  directly.\"\nlicense: MIT\n---\n\n# Find Repeated Work Within One Build\n\nMSBuild runs targets once per project instance. Work that does not depend on the project, but sits in `Directory.Build.targets` or a shared target, therefore runs once per project: a `git rev-parse` in 40 projects is 40 process launches. A project built with different global properties is a different instance, so a shared library can compile several times in one build. The binlog's `N calls` column shows both. This skill finds the repeats, separates them from work that is legitimately per project, and removes only what is safe to remove.\n\n## When to Use\n\n- The same `Exec` or task (version stamping, tool probes, file generation) runs in every project\n- Target or Task Performance Summary shows a call count far above the number of projects that need the work\n- The same project executes its build targets repeatedly under global-property sets that do not change its outputs\n- An `Exec` spawns one process per item in a list\n- A \"run once per build\" guard (`Exists` check, flag property) still runs repeatedly or fails with file-in-use errors under `-m`\n\n## When Not to Use\n\n- Targets that run again on a second, unchanged build: use the incremental-build reference of the `$deniz-dotnet-general:msbuild` skill\n- Slow evaluation before any target runs: use the eval-performance reference of the `$deniz-dotnet-general:msbuild` skill\n- Required project variants colliding in shared bin\u002Fobj directories: use `check-bin-obj-clash`\n- Idle nodes or a serial dependency chain: use `build-parallelism`\n- NuGet restore repeated across separate `dotnet restore`, `dotnet build` and `dotnet test` commands: use `eliminate-redundant-restores`\n- Unranked \"why is my build slow\": use the build-performance route of the `$deniz-dotnet-general:msbuild` skill, which starts from a baseline\n\n## Workflow\n\n### Step 1: Count executions\n\nUse a supplied performance summary with execution counts as valid input; a raw binlog is not required. If the user cannot run the build or forbids execution or new logs, work from the summary and repository files. Mark unavailable timing or overlap evidence `unknown` and proposed fixes `not validated`; do not execute a build or collect another log.\n\nIf neither usable execution counts nor a binlog is supplied, capture one only when build execution is available and permitted. Follow the binlog-generation reference of the `$deniz-dotnet-general:msbuild` skill: add `\u002Fbl:{}` to the original MSBuild invocation, preserving its configuration, global properties, parallelism and restore behavior. In PowerShell, quote the complete switch as `'-bl:{}'`. If a script drives the build, instrument its underlying MSBuild invocation rather than replace it with a different build command. Confirm the binlog exists and record its path. If capture is not permitted, report the missing evidence instead of running the build.\n\nFor an available binlog, when the **binlog MCP server** (`Microsoft.AITools.BinlogMcp`, exposed under the `binlog` MCP namespace) is connected, use it first: discover its available tools and query project, target and task execution counts and timings from that binlog. Do not read the binary file as text.\n\nOtherwise, or when its tools do not expose execution counts, replay the captured binlog to a text performance summary and read the `N calls` column of the Target and Task Performance Summaries and the Project Performance Summary:\n\n```bash\ndotnet msbuild build.binlog -noconlog \"-flp:v=diag;logfile=full.log;performancesummary\"\n```\n\nCount required distinct computations, not just consumers. Derive the expected count separately for each kind of work: `Csc` normally runs once per project and target framework, whereas copy-local work scales with files and can run in several targets. Project count times TFMs is not a universal ceiling for every task; leave an unsupported expected count `unknown` rather than claiming that a larger count is redundant. A multi-targeted project can legitimately show one outer build plus one inner build per TFM, so four project calls for three TFMs are not automatically duplicates. Account for required TFMs and global properties before investigating extra instances.\n\nAn invariant tool-version or revision probe needs one computation per equivalent input scope, even when several projects consume its result. A target condition restricting it to a subset of projects does not make the result per-project. Confirm that inputs, working directories, relevant properties and output semantics are equivalent; identical command text alone does not prove invariance. In particular, fresh per-project signing identities are intentionally nondeterministic: do not cache, reuse or share one identity across projects or builds. Keep each required execution unless a documented tool mode can produce all the distinct results without changing the contract.\n\n### Step 2: Classify each candidate\n\n| Pattern | Signal | Fix | Never |\n|---|---|---|---|\n| Invariant per-project `Exec` or task (commit hash, tool version, generated file) | Multiple consumers need the same deterministic result under equivalent inputs | Compute it once outside the per-project targets: the build script passes `-p:Name=value`, or a pre-build step or orchestrator target runs first | A flag property or `Exists(stamp)` guard: properties are per project instance and `-m` worker nodes are separate processes, so the guard does not dedupe and races |\n| Same project built several times | One project path with N calls and different global properties (for example `Properties=\"ComponentName=%(Component.Filename)\"` on an `MSBuild` task). Any extra global property, even an unused one, creates a new instance | Stop passing the property, or add `GlobalPropertiesToRemove` metadata on the shared `ProjectReference` (`RemoveProperties` on the `MSBuild` task) | Removing a property the project actually reads |\n| One process per item (`Exec` batched on `%(Item.Identity)`) | `Exec` calls equal the item count | One invocation that takes a list or response file, after checking the tool supports it; keep `Inputs`\u002F`Outputs` (with a 1:1 transform MSBuild still passes only the stale items into the target) | Dropping `Inputs`\u002F`Outputs` while merging |\n| Legitimate per-project, per-TFM or per-item work | Count matches the required project, framework or output-item scopes | Leave it alone | Applying one count ceiling to unrelated task kinds |\n\n### Step 3: Size the win\n\nFor eliminated invariant computations, estimate avoidable aggregate task time as `(calls - expected) x average ms`. Per-item batching does not eliminate the required input processing: estimate `(old process starts - new process starts) x startup ms`, retaining every input's processing cost and any required metadata groups. Account for additional list\u002Fbatch overhead when known. If startup cost is unavailable, mark that estimate unknown rather than treating the entire average task duration as removable.\n\nWall-clock saving depends on actual overlap and the critical path. Batched per-item `Exec` calls in one target run sequentially on one node, so avoided startup time is not divided by unrelated busy nodes. Only divide by effective parallelism when the removed work actually overlaps across nodes. Use the binlog timeline to establish overlap, and mark wall-clock savings unknown when that evidence is missing. Work off the critical path can yield no wall-clock gain. For performance-only changes, if even the aggregate upper bound is below about 1% of build wall-clock, report it as not worth changing. Correctness races still need a fix regardless of the timing gain.\n\nFor a cost-based no-change recommendation, show the avoidable aggregate-time bound and, when build elapsed time is supplied, `100 x bound \u002F elapsed` as an upper-bound percentage, not a measured wall-clock gain. Distinguish work that is technically redundant but too cheap to change from work that must remain distinct.\n\n### Step 4: Fix without changing behavior\n\n1. Keep the value available before its first consumer.\n2. Keep a fallback `Condition=\"'$(X)' == ''\"` for builds without the shared value. Imported or environment properties can satisfy it too; the value need not be global. Child builds inherit existing global properties unless removed, but not ordinary properties computed in their parent. Forward a parent-computed result through the `MSBuild` task's `Properties`, or load the shared value in each child before the fallback; otherwise each child can execute its own fallback.\n3. Define the computation in one place.\n4. Preserve generated-file timestamps when content is unchanged. Use a write-if-different generator, or generate to a temporary file and replace only on content change; deduplication must not force dependent recompilation on an unchanged rerun.\n\n```xml\n\u003C!-- Before: every project launches git -->\n\u003CTarget Name=\"StampCommit\" BeforeTargets=\"CoreCompile\">\n  \u003CExec Command=\"git rev-parse HEAD\" ConsoleToMSBuild=\"true\">\n    \u003COutput TaskParameter=\"ConsoleOutput\" PropertyName=\"GitCommit\" \u002F>\n  \u003C\u002FExec>\n\u003C\u002FTarget>\n\n\u003C!-- After: the build script computes the hash once and passes -p:GitCommit=\u003Chash> -->\n\u003CTarget Name=\"StampCommit\" BeforeTargets=\"CoreCompile\">\n  \u003CExec Command=\"git rev-parse HEAD\" ConsoleToMSBuild=\"true\" Condition=\"'$(GitCommit)' == ''\">\n    \u003COutput TaskParameter=\"ConsoleOutput\" PropertyName=\"GitCommit\" \u002F>\n  \u003C\u002FExec>\n\u003C\u002FTarget>\n```\n\nIf Source Link already supplies `SourceRevisionId`, it can replace an `Exec` only when it is available before the consumer and preserves the existing stamp representation. `SourceRevisionId` normally contains the full commit ID; do not substitute it for `git rev-parse --short HEAD` without retaining the original abbreviation contract.\n\n### Step 5: Validate and report truthfully\n\n1. When execution is available and permitted, capture a new binlog of the same invocation. Calls must have dropped to the expected count. Otherwise, do not run the build or collect another log; report the fix as proposed and not validated.\n2. Confirm outputs are unchanged (the stamped value, generated file contents). For generated sources, also check that an unchanged second build stays incremental.\n3. Report timing as the median of at least three runs; if you could not run the build, say \"not validated\".\n\n## Output\n\nFor on-target requests, keep the answer proportional to the evidence: a compact findings table with at least one row, a short explanation of the decisive computation or preservation constraint, and a standalone, unformatted `Verdict:` line. Do not bold the line or append it to a paragraph. Use `unknown` for unavailable timing or critical-path evidence; distinguish estimated aggregate task time from measured wall-clock savings. If the contract requires every execution, report zero avoidable time even when task durations are unknown.\n\n| Work | Calls | Expected | Avoidable ms | Cause | Fix | On critical path? |\n|---|---|---|---|---|---|---|\n\nAfter verification: `Verdict: removed N repeated executions, measured wall-clock saving X s`.\n\nWithout verification: `Verdict: proposed removal of N repeated executions; estimated task-time saving X s; wall-clock not validated`.\n\nWhen no change is worthwhile: `Verdict: no repeated work worth changing`.\n\n## Common Pitfalls\n\n| Pitfall | Solution |\n|---|---|\n| Treating `Csc` or copy-local counts as waste | Compare `Csc` with projects times TFMs, and copies with required files and targets; do not assume both have the same expected count |\n| Guarding with `Exists(file)` or a flag property | Move the work out of the per-project path |\n| Assuming parent-local properties are inherited by child builds | Forward the shared value explicitly or load it in each child before the fallback; otherwise the fallback repeats in those children. Existing global properties are already inherited unless removed. |\n| Claiming a saving from total task time | Check actual overlap and the critical path; do not divide sequential work by unrelated busy nodes |\n| Merging per-item `Exec` and losing incrementality | Keep `Inputs` and `Outputs` on the target |\n","# Find Repeated Work Within One Build\n\nMSBuild runs targets once per project instance. Work that does not depend on the project, but sits in `Directory.Build.targets` or a shared target, therefore runs once per project: a `git rev-parse` in 40 projects is 40 process launches. A project built with different global properties is a different instance, so a shared library can compile several times in one build. The binlog's `N calls` column shows both. This skill finds the repeats, separates them from work that is legitimately per project, and removes only what is safe to remove.\n\n## When to Use\n\n- The same `Exec` or task (version stamping, tool probes, file generation) runs in every project\n- Target or Task Performance Summary shows a call count far above the number of projects that need the work\n- The same project executes its build targets repeatedly under global-property sets that do not change its outputs\n- An `Exec` spawns one process per item in a list\n- A \"run once per build\" guard (`Exists` check, flag property) still runs repeatedly or fails with file-in-use errors under `-m`\n\n## When Not to Use\n\n- Targets that run again on a second, unchanged build: use the incremental-build reference of the `$deniz-dotnet-general:msbuild` skill\n- Slow evaluation before any target runs: use the eval-performance reference of the `$deniz-dotnet-general:msbuild` skill\n- Required project variants colliding in shared bin\u002Fobj directories: use `check-bin-obj-clash`\n- Idle nodes or a serial dependency chain: use `build-parallelism`\n- NuGet restore repeated across separate `dotnet restore`, `dotnet build` and `dotnet test` commands: use `eliminate-redundant-restores`\n- Unranked \"why is my build slow\": use the build-performance route of the `$deniz-dotnet-general:msbuild` skill, which starts from a baseline\n\n## Workflow\n\n### Step 1: Count executions\n\nUse a supplied performance summary with execution counts as valid input; a raw binlog is not required. If the user cannot run the build or forbids execution or new logs, work from the summary and repository files. Mark unavailable timing or overlap evidence `unknown` and proposed fixes `not validated`; do not execute a build or collect another log.\n\nIf neither usable execution counts nor a binlog is supplied, capture one only when build execution is available and permitted. Follow the binlog-generation reference of the `$deniz-dotnet-general:msbuild` skill: add `\u002Fbl:{}` to the original MSBuild invocation, preserving its configuration, global properties, parallelism and restore behavior. In PowerShell, quote the complete switch as `'-bl:{}'`. If a script drives the build, instrument its underlying MSBuild invocation rather than replace it with a different build command. Confirm the binlog exists and record its path. If capture is not permitted, report the missing evidence instead of running the build.\n\nFor an available binlog, when the **binlog MCP server** (`Microsoft.AITools.BinlogMcp`, exposed under the `binlog` MCP namespace) is connected, use it first: discover its available tools and query project, target and task execution counts and timings from that binlog. Do not read the binary file as text.\n\nOtherwise, or when its tools do not expose execution counts, replay the captured binlog to a text performance summary and read the `N calls` column of the Target and Task Performance Summaries and the Project Performance Summary:\n\n```bash\ndotnet msbuild build.binlog -noconlog \"-flp:v=diag;logfile=full.log;performancesummary\"\n```\n\nCount required distinct computations, not just consumers. Derive the expected count separately for each kind of work: `Csc` normally runs once per project and target framework, whereas copy-local work scales with files and can run in several targets. Project count times TFMs is not a universal ceiling for every task; leave an unsupported expected count `unknown` rather than claiming that a larger count is redundant. A multi-targeted project can legitimately show one outer build plus one inner build per TFM, so four project calls for three TFMs are not automatically duplicates. Account for required TFMs and global properties before investigating extra instances.\n\nAn invariant tool-version or revision probe needs one computation per equivalent input scope, even when several projects consume its result. A target condition restricting it to a subset of projects does not make the result per-project. Confirm that inputs, working directories, relevant properties and output semantics are equivalent; identical command text alone does not prove invariance. In particular, fresh per-project signing identities are intentionally nondeterministic: do not cache, reuse or share one identity across projects or builds. Keep each required execution unless a documented tool mode can produce all the distinct results without changing the contract.\n\n### Step 2: Classify each candidate\n\n| Pattern | Signal | Fix | Never |\n|---|---|---|---|\n| Invariant per-project `Exec` or task (commit hash, tool version, generated file) | Multiple consumers need the same deterministic result under equivalent inputs | Compute it once outside the per-project targets: the build script passes `-p:Name=value`, or a pre-build step or orchestrator target runs first | A flag property or `Exists(stamp)` guard: properties are per project instance and `-m` worker nodes are separate processes, so the guard does not dedupe and races |\n| Same project built several times | One project path with N calls and different global properties (for example `Properties=\"ComponentName=%(Component.Filename)\"` on an `MSBuild` task). Any extra global property, even an unused one, creates a new instance | Stop passing the property, or add `GlobalPropertiesToRemove` metadata on the shared `ProjectReference` (`RemoveProperties` on the `MSBuild` task) | Removing a property the project actually reads |\n| One process per item (`Exec` batched on `%(Item.Identity)`) | `Exec` calls equal the item count | One invocation that takes a list or response file, after checking the tool supports it; keep `Inputs`\u002F`Outputs` (with a 1:1 transform MSBuild still passes only the stale items into the target) | Dropping `Inputs`\u002F`Outputs` while merging |\n| Legitimate per-project, per-TFM or per-item work | Count matches the required project, framework or output-item scopes | Leave it alone | Applying one count ceiling to unrelated task kinds |\n\n### Step 3: Size the win\n\nFor eliminated invariant computations, estimate avoidable aggregate task time as `(calls - expected) x average ms`. Per-item batching does not eliminate the required input processing: estimate `(old process starts - new process starts) x startup ms`, retaining every input's processing cost and any required metadata groups. Account for additional list\u002Fbatch overhead when known. If startup cost is unavailable, mark that estimate unknown rather than treating the entire average task duration as removable.\n\nWall-clock saving depends on actual overlap and the critical path. Batched per-item `Exec` calls in one target run sequentially on one node, so avoided startup time is not divided by unrelated busy nodes. Only divide by effective parallelism when the removed work actually overlaps across nodes. Use the binlog timeline to establish overlap, and mark wall-clock savings unknown when that evidence is missing. Work off the critical path can yield no wall-clock gain. For performance-only changes, if even the aggregate upper bound is below about 1% of build wall-clock, report it as not worth changing. Correctness races still need a fix regardless of the timing gain.\n\nFor a cost-based no-change recommendation, show the avoidable aggregate-time bound and, when build elapsed time is supplied, `100 x bound \u002F elapsed` as an upper-bound percentage, not a measured wall-clock gain. Distinguish work that is technically redundant but too cheap to change from work that must remain distinct.\n\n### Step 4: Fix without changing behavior\n\n1. Keep the value available before its first consumer.\n2. Keep a fallback `Condition=\"'$(X)' == ''\"` for builds without the shared value. Imported or environment properties can satisfy it too; the value need not be global. Child builds inherit existing global properties unless removed, but not ordinary properties computed in their parent. Forward a parent-computed result through the `MSBuild` task's `Properties`, or load the shared value in each child before the fallback; otherwise each child can execute its own fallback.\n3. Define the computation in one place.\n4. Preserve generated-file timestamps when content is unchanged. Use a write-if-different generator, or generate to a temporary file and replace only on content change; deduplication must not force dependent recompilation on an unchanged rerun.\n\n```xml\n\u003C!-- Before: every project launches git -->\n\u003CTarget Name=\"StampCommit\" BeforeTargets=\"CoreCompile\">\n  \u003CExec Command=\"git rev-parse HEAD\" ConsoleToMSBuild=\"true\">\n    \u003COutput TaskParameter=\"ConsoleOutput\" PropertyName=\"GitCommit\" \u002F>\n  \u003C\u002FExec>\n\u003C\u002FTarget>\n\n\u003C!-- After: the build script computes the hash once and passes -p:GitCommit=\u003Chash> -->\n\u003CTarget Name=\"StampCommit\" BeforeTargets=\"CoreCompile\">\n  \u003CExec Command=\"git rev-parse HEAD\" ConsoleToMSBuild=\"true\" Condition=\"'$(GitCommit)' == ''\">\n    \u003COutput TaskParameter=\"ConsoleOutput\" PropertyName=\"GitCommit\" \u002F>\n  \u003C\u002FExec>\n\u003C\u002FTarget>\n```\n\nIf Source Link already supplies `SourceRevisionId`, it can replace an `Exec` only when it is available before the consumer and preserves the existing stamp representation. `SourceRevisionId` normally contains the full commit ID; do not substitute it for `git rev-parse --short HEAD` without retaining the original abbreviation contract.\n\n### Step 5: Validate and report truthfully\n\n1. When execution is available and permitted, capture a new binlog of the same invocation. Calls must have dropped to the expected count. Otherwise, do not run the build or collect another log; report the fix as proposed and not validated.\n2. Confirm outputs are unchanged (the stamped value, generated file contents). For generated sources, also check that an unchanged second build stays incremental.\n3. Report timing as the median of at least three runs; if you could not run the build, say \"not validated\".\n\n## Output\n\nFor on-target requests, keep the answer proportional to the evidence: a compact findings table with at least one row, a short explanation of the decisive computation or preservation constraint, and a standalone, unformatted `Verdict:` line. Do not bold the line or append it to a paragraph. Use `unknown` for unavailable timing or critical-path evidence; distinguish estimated aggregate task time from measured wall-clock savings. If the contract requires every execution, report zero avoidable time even when task durations are unknown.\n\n| Work | Calls | Expected | Avoidable ms | Cause | Fix | On critical path? |\n|---|---|---|---|---|---|---|\n\nAfter verification: `Verdict: removed N repeated executions, measured wall-clock saving X s`.\n\nWithout verification: `Verdict: proposed removal of N repeated executions; estimated task-time saving X s; wall-clock not validated`.\n\nWhen no change is worthwhile: `Verdict: no repeated work worth changing`.\n\n## Common Pitfalls\n\n| Pitfall | Solution |\n|---|---|\n| Treating `Csc` or copy-local counts as waste | Compare `Csc` with projects times TFMs, and copies with required files and targets; do not assume both have the same expected count |\n| Guarding with `Exists(file)` or a flag property | Move the work out of the per-project path |\n| Assuming parent-local properties are inherited by child builds | Forward the shared value explicitly or load it in each child before the fallback; otherwise the fallback repeats in those children. Existing global properties are already inherited unless removed. |\n| Claiming a saving from total task time | Check actual overlap and the critical path; do not divide sequential work by unrelated busy nodes |\n| Merging per-item `Exec` and losing incrementality | Keep `Inputs` and `Outputs` on the target |\n",{"name":5,"license":15,"description":7},"master","b30b1c1908dbc56a8184128f18803053d762ccb5","codex\u002Fdeniz-dotnet-general\u002Fskills\u002Ffind-repeated-work-within-one-build",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 find-repeated-work-within-one-build",{"tool":39,"command":40},"bunx","bunx skills add Blind-Striker\u002Fagent-skills-and-plugins --skill find-repeated-work-within-one-build",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Blind-Striker\u002Fagent-skills-and-plugins --skill find-repeated-work-within-one-build","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fcodex\u002Fdeniz-dotnet-general\u002Fskills\u002Ffind-repeated-work-within-one-build\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"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":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"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":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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",[],[]]