[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DZPKR0DR5FACA06GDVED8K":3,"skill-same:01M6DZPKR0DR5FACA06GDVED8K":113},{"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":23,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6DZPKR0DR5FACA06GDVED8K","test-smell-detection",null,"Audits existing tests in any language using formal, research-backed test smell names and the testsmells.org 19-smell academic taxonomy. Use when the caller asks for an academic or citable test-smell review, named smell categories, or a formal severity-ranked smell assessment. Covers Assertion Roulette, Conditional Test Logic, Mystery Guest, Eager Test, Sleepy Test, Unknown Test, Sensitive Equality, and the rest of the catalog across .NET, Python, JavaScript\u002FTypeScript, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, and C++. DO NOT USE FOR a quick pragmatic test review (use test-anti-patterns), writing or running tests, framework migration, coverage, or assertion-diversity metrics.","managedcode\u002Fdotnet-skills","managedcode","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F78253589?v=4","01M6DYDJR3EG8KB5G4PC65XCTT","Managed Code","01M6DYDJX0ZT432N04NYJW89DN",512,"MIT","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fexternal-sources\u002Fupstreams\u002Fdotnet-skills\u002Fplugins\u002Fdotnet-test\u002Fskills\u002Ftest-smell-detection\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"test","test smell detection","detection","when","writing","unknown","categories","quick","org","across","pragmatic","patterns","do","anti-patterns","coverage","ruby","powershell","metrics","framework","assessment","rust","go","typescript","review","swift","2026-11-10 10:12:30",false,"---\nname: test-smell-detection\ndescription: >\n  Audits existing tests in any language using formal, research-backed test\n  smell names and the testsmells.org 19-smell academic taxonomy. Use when the\n  caller asks for an academic or citable test-smell review, named smell\n  categories, or a formal severity-ranked smell assessment. Covers Assertion\n  Roulette, Conditional Test Logic, Mystery Guest, Eager Test, Sleepy Test,\n  Unknown Test, Sensitive Equality, and the rest of the catalog across .NET,\n  Python, JavaScript\u002FTypeScript, Java, Go, Ruby, Rust, Swift, Kotlin,\n  PowerShell, and C++. DO NOT USE FOR a quick pragmatic test review (use\n  test-anti-patterns), writing or running tests, framework migration, coverage,\n  or assertion-diversity metrics.\nlicense: MIT\n---\n\n# Test Smell Detection\n\nAudit test code with the academic taxonomy, code evidence, calibrated\nframework idioms, and fixes native to the codebase.\n\n## Scope\n\n- Audit only staged or named tests. Search the current workspace before asking\n  for code; never claim a file is missing until that search finds no relevant\n  test.\n- Read production code only when it changes a verdict.\n- For unfamiliar framework APIs, read the matching language file relative to\n  the caller-provided or runtime-listed `test-analysis-extensions` catalog,\n  not a skill invocation. If absent, use the framework and rules here and report\n  the missing reference; do not search installation directories.\n- Read [the complete catalog](references\u002Ftest-smell-catalog.md) when the caller\n  requests all 19 smells, asks for citations, or the code may contain a smell\n  outside the high-signal set below. Do not load it for a narrow question that\n  this file answers.\n\n## Audit Workflow\n\n1. Search for and read the staged tests; detect language, framework, boundaries,\n   and integration markers. This is the first action even when no path is named.\n2. Read the tests and only verdict-changing production context.\n3. For each candidate, verify the executed check, choose the formal category,\n   calibrate, then assign severity. Report proven non-catalog test-validity\n   defects separately; do not relabel them as smells.\n4. Rank confirmed findings by risk of false confidence or flakiness, then by\n   maintenance cost.\n5. Give a framework-correct replacement for each actionable finding. Never use\n   .NET terminology or APIs in another ecosystem.\n\n## High-Signal Decisions\n\n| Evidence | Academic finding | Do | Never |\n|---|---|---|---|\n| Assertion behavior changes behind `if`, `switch`, or branching loops | Conditional Test Logic | Split cases or parameterize them | Flag table-driven or parametrized tests merely because a runner loop exists |\n| A test relies on an undeclared file, network service, environment value, or database | Mystery Guest or Resource Optimism | Make the dependency explicit and hermetic; distinguish the two using the full catalog | Condemn an integration test merely for exercising its declared real resource |\n| Fixed wall-clock sleep waits for an outcome | Sleepy Test | Await or poll the condition with a timeout | Downgrade it only because the test is an integration test |\n| Executable test has no assertion, expected-exception marker, or mock verification | Unknown Test | Assert the observable outcome | Call an empty body Unknown Test; the formal name is Empty Test |\n| Async assertion\u002Fcoroutine is created but not awaited or returned | Critical non-catalog false-pass defect | Report it separately and show the required `await`\u002F`return` | Force it into Unknown Test; the assertion statement exists |\n| One test exercises many unrelated production behaviors | Eager Test | Separate behavior-focused tests | Flag a deliberate end-to-end workflow without considering its scope |\n| Expected numeric literal has no local meaning | Magic Number Test | Name the domain value or derive it from setup | Flag `count == 3` immediately after adding three items |\n| Assertion depends on `ToString`, `repr`, `description`, or display formatting that is not the contract | Sensitive Equality | Assert stable fields or use a structural matcher | Flag a test whose explicit contract is the formatted string |\n| Test manually manages expected exception flow | Exception Handling | Use the framework's exception assertion and check meaningful details | Claim a capture-and-assert test verifies nothing |\n| Shared setup creates state irrelevant to the tests that receive it | General Fixture | Remove unused state or narrow the fixture; rank cheap state low | Condemn relevant shared setup merely because it is shared |\n| Test is disabled or skipped | Ignored Test | Report every skip, but rank a tracked, reasoned skip below an unexplained one | Clear a skip because its reason is good, or give both the same urgency |\n\n## Calibration Rules\n\nApply these before assigning a finding:\n\n- Mock-call verifications, snapshots, bare pytest `assert`, Pester\n  `Should -Invoke`, and expected-exception constructs are assertions.\n- A literal or snapshot assertion may expose a coverage gap, but is not Unknown\n  Test or another smell without separate evidence.\n- Count assertion statements. One assertion is never Assertion Roulette;\n  missing messages alone are not a smell.\n- Same-method tests are not Lazy Test when they cover distinct behaviors,\n  boundaries, or state; require redundant equivalent paths.\n- General Fixture requires shared lifecycle state. Repeated local construction\n  is neither General Fixture nor Test Code Duplication by itself.\n- Treat strings returned by the public API as observable contract unless\n  production context or requirements make them display-only; interpolation\n  alone is not Sensitive Equality.\n- Magic Number Test requires an unexplained oracle value. Do not flag ordinary\n  setup quantities whose role is locally obvious and irrelevant to the asserted\n  behavior.\n- Go table-driven subtests, pytest\u002FJUnit\u002FxUnit parameterization, Jest\u002FVitest\n  `.each`, RSpec data tables, Pester `-ForEach`, and Catch2\n  `SECTION`\u002F`GENERATE` are not Conditional Test Logic by themselves.\n- Go's `if err != nil { t.Fatal(...) }` is idiomatic assertion flow, not\n  Exception Handling.\n- Integration markers legitimize declared external resources and multi-step\n  flows, but not fixed sleeps or assertion-free execution.\n- For integration tests, trace helper factories and repository return types\n  before judging branch coverage. If a test branches on a subtype or state that\n  the real helper can never produce, report the unreachable assertion path and\n  explain the resulting false confidence. Do not stop at assigning the generic\n  Conditional Test Logic label.\n- A local temporary file still meets the formal Mystery Guest definition.\n  Hermetic creation and cleanup reduce its severity; they do not change its\n  taxonomy.\n- A formatting name does not prove display text is the stable contract; confirm\n  it from production behavior or requirements before clearing Sensitive\n  Equality.\n- Do not infer a smell from method names alone. Point to the statement or\n  fixture relationship that proves it.\n- Do not infer a high-severity non-catalog validity defect from a test name\n  alone. Without production code or an explicit contract proving that the test\n  is supposed to invoke another component, a name\u002Fbody mismatch is at most an\n  unranked observation, not evidence that the test silently passes broken\n  production behavior.\n- Catch2 `SECTION` and `GENERATE` are runner-controlled case expansion, and\n  `REQUIRE` is a real assertion. When those are the only suspicious constructs,\n  the academic-smell verdict is **clean**. Do not reverse that verdict because\n  the test could have broader behavioral coverage.\n- If no material smell remains after calibration, say that clearly. Never\n  manufacture findings to fill a report.\n- Never propose `await` for a void or otherwise non-awaitable API. If production\n  work is synchronous, remove the sleep and assert immediately.\n\n## Severity\n\nSeverity follows demonstrated risk, not a fixed label copied from the catalog:\n\n- **High:** can silently pass while behavior is broken, creates\n  nondeterministic failures, or hides unexecuted assertion paths.\n- **Medium:** makes failures ambiguous or couples tests to unstable details.\n- **Low:** primarily maintenance debt, such as a reasoned skip or over-broad\n  cheap fixture.\n\nState the reason for the assigned severity. Downgrade or omit a finding when\nthe surrounding test type makes the pattern intentional.\n\n## Output Contract\n\nScale the response to the input:\n\n- For one to three files, give a verdict and one compact table: severity,\n  formal smell, evidence, risk, and fix.\n- For larger suites, add counts and a short priority order. Do not repeat\n  findings across dashboards, prose, and plans.\n- Show code only when it clarifies a fix; omit unchanged setup.\n- Add brief **Not findings** only for plausibly suspicious idioms.\n- Put proven non-catalog validity defects after the academic-smell verdict. On a\n  clean input with no production contract, do not assign severity to optional\n  coverage observations or let them overturn the clean verdict.\n- Do not narrate discovery or catalog loading; return the audit directly.\n\nEvery reported smell must have a formal taxonomy name, precise location,\nevidence from the code, practical risk, and a concrete framework-correct fix.\n\n## Validation\n\n- Every finding is supported by code, not a keyword or method name.\n- Unknown Test and Empty Test remain distinct.\n- Every disabled test remains Ignored Test, and every local file dependency\n  remains Mystery Guest; rationale and hermetic cleanup change severity only.\n- Framework idioms and integration boundaries were calibrated before reporting.\n- Clean tests and suspicious-but-valid idioms are not turned into filler.\n- Clean framework idioms are not converted into high-severity non-catalog\n  findings from naming or absent production context.\n- Fixes use the target framework's APIs and preserve the behavior under test.\n- Claims about files reviewed, builds, or test runs match actions actually\n  performed.\n","# Test Smell Detection\n\nAudit test code with the academic taxonomy, code evidence, calibrated\nframework idioms, and fixes native to the codebase.\n\n## Scope\n\n- Audit only staged or named tests. Search the current workspace before asking\n  for code; never claim a file is missing until that search finds no relevant\n  test.\n- Read production code only when it changes a verdict.\n- For unfamiliar framework APIs, read the matching language file relative to\n  the caller-provided or runtime-listed `test-analysis-extensions` catalog,\n  not a skill invocation. If absent, use the framework and rules here and report\n  the missing reference; do not search installation directories.\n- Read [the complete catalog](references\u002Ftest-smell-catalog.md) when the caller\n  requests all 19 smells, asks for citations, or the code may contain a smell\n  outside the high-signal set below. Do not load it for a narrow question that\n  this file answers.\n\n## Audit Workflow\n\n1. Search for and read the staged tests; detect language, framework, boundaries,\n   and integration markers. This is the first action even when no path is named.\n2. Read the tests and only verdict-changing production context.\n3. For each candidate, verify the executed check, choose the formal category,\n   calibrate, then assign severity. Report proven non-catalog test-validity\n   defects separately; do not relabel them as smells.\n4. Rank confirmed findings by risk of false confidence or flakiness, then by\n   maintenance cost.\n5. Give a framework-correct replacement for each actionable finding. Never use\n   .NET terminology or APIs in another ecosystem.\n\n## High-Signal Decisions\n\n| Evidence | Academic finding | Do | Never |\n|---|---|---|---|\n| Assertion behavior changes behind `if`, `switch`, or branching loops | Conditional Test Logic | Split cases or parameterize them | Flag table-driven or parametrized tests merely because a runner loop exists |\n| A test relies on an undeclared file, network service, environment value, or database | Mystery Guest or Resource Optimism | Make the dependency explicit and hermetic; distinguish the two using the full catalog | Condemn an integration test merely for exercising its declared real resource |\n| Fixed wall-clock sleep waits for an outcome | Sleepy Test | Await or poll the condition with a timeout | Downgrade it only because the test is an integration test |\n| Executable test has no assertion, expected-exception marker, or mock verification | Unknown Test | Assert the observable outcome | Call an empty body Unknown Test; the formal name is Empty Test |\n| Async assertion\u002Fcoroutine is created but not awaited or returned | Critical non-catalog false-pass defect | Report it separately and show the required `await`\u002F`return` | Force it into Unknown Test; the assertion statement exists |\n| One test exercises many unrelated production behaviors | Eager Test | Separate behavior-focused tests | Flag a deliberate end-to-end workflow without considering its scope |\n| Expected numeric literal has no local meaning | Magic Number Test | Name the domain value or derive it from setup | Flag `count == 3` immediately after adding three items |\n| Assertion depends on `ToString`, `repr`, `description`, or display formatting that is not the contract | Sensitive Equality | Assert stable fields or use a structural matcher | Flag a test whose explicit contract is the formatted string |\n| Test manually manages expected exception flow | Exception Handling | Use the framework's exception assertion and check meaningful details | Claim a capture-and-assert test verifies nothing |\n| Shared setup creates state irrelevant to the tests that receive it | General Fixture | Remove unused state or narrow the fixture; rank cheap state low | Condemn relevant shared setup merely because it is shared |\n| Test is disabled or skipped | Ignored Test | Report every skip, but rank a tracked, reasoned skip below an unexplained one | Clear a skip because its reason is good, or give both the same urgency |\n\n## Calibration Rules\n\nApply these before assigning a finding:\n\n- Mock-call verifications, snapshots, bare pytest `assert`, Pester\n  `Should -Invoke`, and expected-exception constructs are assertions.\n- A literal or snapshot assertion may expose a coverage gap, but is not Unknown\n  Test or another smell without separate evidence.\n- Count assertion statements. One assertion is never Assertion Roulette;\n  missing messages alone are not a smell.\n- Same-method tests are not Lazy Test when they cover distinct behaviors,\n  boundaries, or state; require redundant equivalent paths.\n- General Fixture requires shared lifecycle state. Repeated local construction\n  is neither General Fixture nor Test Code Duplication by itself.\n- Treat strings returned by the public API as observable contract unless\n  production context or requirements make them display-only; interpolation\n  alone is not Sensitive Equality.\n- Magic Number Test requires an unexplained oracle value. Do not flag ordinary\n  setup quantities whose role is locally obvious and irrelevant to the asserted\n  behavior.\n- Go table-driven subtests, pytest\u002FJUnit\u002FxUnit parameterization, Jest\u002FVitest\n  `.each`, RSpec data tables, Pester `-ForEach`, and Catch2\n  `SECTION`\u002F`GENERATE` are not Conditional Test Logic by themselves.\n- Go's `if err != nil { t.Fatal(...) }` is idiomatic assertion flow, not\n  Exception Handling.\n- Integration markers legitimize declared external resources and multi-step\n  flows, but not fixed sleeps or assertion-free execution.\n- For integration tests, trace helper factories and repository return types\n  before judging branch coverage. If a test branches on a subtype or state that\n  the real helper can never produce, report the unreachable assertion path and\n  explain the resulting false confidence. Do not stop at assigning the generic\n  Conditional Test Logic label.\n- A local temporary file still meets the formal Mystery Guest definition.\n  Hermetic creation and cleanup reduce its severity; they do not change its\n  taxonomy.\n- A formatting name does not prove display text is the stable contract; confirm\n  it from production behavior or requirements before clearing Sensitive\n  Equality.\n- Do not infer a smell from method names alone. Point to the statement or\n  fixture relationship that proves it.\n- Do not infer a high-severity non-catalog validity defect from a test name\n  alone. Without production code or an explicit contract proving that the test\n  is supposed to invoke another component, a name\u002Fbody mismatch is at most an\n  unranked observation, not evidence that the test silently passes broken\n  production behavior.\n- Catch2 `SECTION` and `GENERATE` are runner-controlled case expansion, and\n  `REQUIRE` is a real assertion. When those are the only suspicious constructs,\n  the academic-smell verdict is **clean**. Do not reverse that verdict because\n  the test could have broader behavioral coverage.\n- If no material smell remains after calibration, say that clearly. Never\n  manufacture findings to fill a report.\n- Never propose `await` for a void or otherwise non-awaitable API. If production\n  work is synchronous, remove the sleep and assert immediately.\n\n## Severity\n\nSeverity follows demonstrated risk, not a fixed label copied from the catalog:\n\n- **High:** can silently pass while behavior is broken, creates\n  nondeterministic failures, or hides unexecuted assertion paths.\n- **Medium:** makes failures ambiguous or couples tests to unstable details.\n- **Low:** primarily maintenance debt, such as a reasoned skip or over-broad\n  cheap fixture.\n\nState the reason for the assigned severity. Downgrade or omit a finding when\nthe surrounding test type makes the pattern intentional.\n\n## Output Contract\n\nScale the response to the input:\n\n- For one to three files, give a verdict and one compact table: severity,\n  formal smell, evidence, risk, and fix.\n- For larger suites, add counts and a short priority order. Do not repeat\n  findings across dashboards, prose, and plans.\n- Show code only when it clarifies a fix; omit unchanged setup.\n- Add brief **Not findings** only for plausibly suspicious idioms.\n- Put proven non-catalog validity defects after the academic-smell verdict. On a\n  clean input with no production contract, do not assign severity to optional\n  coverage observations or let them overturn the clean verdict.\n- Do not narrate discovery or catalog loading; return the audit directly.\n\nEvery reported smell must have a formal taxonomy name, precise location,\nevidence from the code, practical risk, and a concrete framework-correct fix.\n\n## Validation\n\n- Every finding is supported by code, not a keyword or method name.\n- Unknown Test and Empty Test remain distinct.\n- Every disabled test remains Ignored Test, and every local file dependency\n  remains Mystery Guest; rationale and hermetic cleanup change severity only.\n- Framework idioms and integration boundaries were calibrated before reporting.\n- Clean tests and suspicious-but-valid idioms are not turned into filler.\n- Clean framework idioms are not converted into high-severity non-catalog\n  findings from naming or absent production context.\n- Fixes use the target framework's APIs and preserve the behavior under test.\n- Claims about files reviewed, builds, or test runs match actions actually\n  performed.\n",{"name":5,"license":15,"description":54},"Audits existing tests in any language using formal, research-backed test smell names and the testsmells.org 19-smell academic taxonomy. Use when the caller asks for an academic or citable test-smell review, named smell categories, or a formal severity-ranked smell assessment. Covers Assertion Roulette, Conditional Test Logic, Mystery Guest, Eager Test, Sleepy Test, Unknown Test, Sensitive Equality, and the rest of the catalog across .NET, Python, JavaScript\u002FTypeScript, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, and C++. DO NOT USE FOR a quick pragmatic test review (use test-anti-patterns), writing or running tests, framework migration, coverage, or assertion-diversity metrics.\n","main","497cc9aba79a931ac6fb8d36a48cc22fe3d6d74b","external-sources\u002Fupstreams\u002Fdotnet-skills\u002Fplugins\u002Fdotnet-test\u002Fskills\u002Ftest-smell-detection",41,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills","https:\u002F\u002Fskills.managed-code.com","https:\u002F\u002Fgithub.com\u002Fmanagedcode","https:\u002F\u002Fwww.managed-code.com","Open Source Community for .NET Developers: Reliable, Actively Maintained, and Community-Driven. Made in Ukraine 🇺🇦 with ❤️","2026-11-11 19:34:28",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add managedcode\u002Fdotnet-skills --skill test-smell-detection",{"tool":71,"command":72},"bunx","bunx skills add managedcode\u002Fdotnet-skills --skill test-smell-detection",{"tool":74,"command":75},"pnpm","pnpm dlx skills add managedcode\u002Fdotnet-skills --skill test-smell-detection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fexternal-sources\u002Fupstreams\u002Fdotnet-skills\u002Fplugins\u002Fdotnet-test\u002Fskills\u002Ftest-smell-detection\u002FSKILL.md",true,[79,85,89,93,97,101,105,109],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fagentic-setup.md","REFERENCE","参考文档",3058,"https:\u002F\u002Fgithub.com\u002Ftkogut\u002Fagents-os-core\u002Fblob\u002Fmaster\u002Fglobal_skills\u002Fom-auto-qa-pr\u002Freferences\u002Fagentic-setup.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fboot-env.md",2393,"https:\u002F\u002Fgithub.com\u002Ftkogut\u002Fagents-os-core\u002Fblob\u002Fmaster\u002Fglobal_skills\u002Fom-auto-qa-pr\u002Freferences\u002Fboot-env.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fclaim-pr.md",8284,"https:\u002F\u002Fgithub.com\u002Ftkogut\u002Fagents-os-core\u002Fblob\u002Fmaster\u002Fglobal_skills\u002Fom-auto-qa-pr\u002Freferences\u002Fclaim-pr.md",{"path":94,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fdriving-scenario.md",2104,"https:\u002F\u002Fgithub.com\u002Ftkogut\u002Fagents-os-core\u002Fblob\u002Fmaster\u002Fglobal_skills\u002Fom-auto-qa-pr\u002Freferences\u002Fdriving-scenario.md",{"path":98,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Freport-templates.md",3540,"https:\u002F\u002Fgithub.com\u002Ftkogut\u002Fagents-os-core\u002Fblob\u002Fmaster\u002Fglobal_skills\u002Fom-auto-qa-pr\u002Freferences\u002Freport-templates.md",{"path":102,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Frules.md",5435,"https:\u002F\u002Fgithub.com\u002Ftkogut\u002Fagents-os-core\u002Fblob\u002Fmaster\u002Fglobal_skills\u002Fom-auto-qa-pr\u002Freferences\u002Frules.md",{"path":106,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Ftest-smell-catalog.md",6453,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fexternal-sources\u002Fupstreams\u002Fdotnet-skills\u002Fplugins\u002Fdotnet-test\u002Fskills\u002Ftest-smell-detection\u002Freferences\u002Ftest-smell-catalog.md",{"path":110,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fworktree-setup.md",2080,"https:\u002F\u002Fgithub.com\u002Ftkogut\u002Fagents-os-core\u002Fblob\u002Fmaster\u002Fglobal_skills\u002Fom-auto-qa-pr\u002Freferences\u002Fworktree-setup.md",[114,149,172,203,213,240],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":128,"publishedAt":49},"01M6DYQE1Y9FHAQHEDTVFQ3447","xtwitter-scraper","Use XTwitterScraper when a .NET application needs typed access to Xquik's X automation REST API for tweet search, user lookup, posting workflows, extraction jobs, monitors, webhooks, or giveaway draws. USE FOR: integrating the XTwitterScraper NuGet package; reviewing Xquik API client usage; modeling API-key configuration, pagination, binary exports, raw responses, retries, and webhook\u002Fevent flows in .NET. DO NOT USE FOR: unrelated stacks; direct browser automation; generic social-media strategy; or code that does not call Xquik. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FLibraries\u002FXTwitterScraper\u002Fskills\u002Fxtwitter-scraper\u002FSKILL.md",[120,123],{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":124,"categoryName":125,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148],"xtwitter scraper","browser automation","workflows","run","code","browser","search","repository","api","Media","api client","access","edit","unrelated","webhooks","files","social","commands","modeling","webhook",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":161,"publishedAt":49},"01M6DYQ9S4PE1H6G8MCH9T21HR","sep","Use Sep for high-performance separated-value parsing and writing in .NET, including delimiter inference, explicit parser\u002Fwriter options, and low-allocation row\u002Fcolumn workflows. USE FOR: delimited data needs are performance-sensitive and allocation-aware; project needs explicit control over separator inference, escaping, trimming, and header behavior;. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FLibraries\u002FSep\u002Fskills\u002Fsep\u002FSKILL.md",[155,158],{"categoryNo":156,"categoryName":157,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":159,"categoryName":160,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000036","内容创作者",[151,28,162,131,163,132,136,164,165,166,141,167,142,144,36,168,169,170,146,171],"performance","tasks","data","parsing","parser","context","writer","options","project","high-performance",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":178,"publishedAt":49},"01M6DZS2DNEPXCGGF6SSCW6G5V","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fexternal-sources\u002Fupstreams\u002Fwebgpu-claude-skill\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,27],"webgpu","threejs","webgpu threejs tsl","setup","shaders","gpu","integration","applications","js","node","syntax","guide","use","language","three","compute","post","processing","with","renderer","for","materials","wgsl","effects",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":209,"publishedAt":49},"01M6DZS0BQXW2B56A289XF1X76","roslynk","Use Roslynk for semantic inspection and edits of *.cs, *.razor and *.cshtml solution files.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fexternal-sources\u002Fupstreams\u002Froslynk\u002Fskills\u002Froslynk\u002FSKILL.md",[],[205,191,144,210,211,199,212],"semantic","razor","inspection",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":219,"publishedAt":49},"01M6DZRW6MEJCVW80K3S4XV60K","system-text-json-net11","Imperative guidance for the System.Text.Json APIs added in .NET 11: the built-in `JsonNamingPolicy.PascalCase` naming policy, and the strongly-typed generic `JsonSerializerOptions.GetTypeInfo` and `JsonSerializerOptions.TryGetTypeInfo` metadata accessors (generic overloads that return a typed `JsonTypeInfo`). USE ONLY when the user is targeting net11.0 or later and needs PascalCase JSON property or dictionary-key names without writing a custom naming policy, a strongly-typed generic `JsonTypeInfo` instead of the non-generic `JsonTypeInfo`, or a no-throw way to probe whether a type's serialization metadata is resolved. DO NOT USE when the target is earlier than net11.0, the requested behavior uses an established pre-net11 naming policy, or the user explicitly selected another JSON library.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fexternal-sources\u002Fupstreams\u002Fdotnet-skills\u002Fplugins\u002Fdotnet11\u002Fskills\u002Fsystem-text-json-net11\u002FSKILL.md",[],[220,221,222,223,28,224,225,226,227,228,229,191,230,231,232,233,36,234,235,236,237,199,238,239,27],"system","json","text","system text json net11","policy","metadata","library","serialization","behavior","user","only","probe","guidance","later","type","dictionary","naming","targeting","custom","generic",{"skillNo":241,"name":242,"nameZh":6,"description":243,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":244,"categories":245,"keywords":248,"publishedAt":49},"01M6DZRRJP3S662NFSG1RSPQQ7","process-api-net11","Provides guidance on the new System.Diagnostics.Process APIs introduced in .NET 11: Process.Run, Process.RunAndCaptureText, Process.StartAndForget, Process.ReadAllText\u002FBytes\u002FLines, KillOnParentExit, InheritedHandles, and StartDetached. USE FOR: starting, orchestrating, or capturing output from external processes in applications targeting net11.0 or later. DO NOT USE FOR: applications targeting .NET 10 or earlier, or basic pre-.NET 11 Process.Start usage without new APIs.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fexternal-sources\u002Fupstreams\u002Fdotnet-skills\u002Fplugins\u002Fdotnet11\u002Fskills\u002Fprocess-api-net11\u002FSKILL.md",[246,247],{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":124,"categoryName":125,"taxonomyType":126,"taxonomyTypeDesc":127},[137,249,250,251,132,252,186,220,191,232,233,36,253,254,255,256,237,199,257],"process","process api net11","diagnostics","start","basic","processes","output","usage","new"]