[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D281MFHHWHGMXR1TBECTQM":3,"skill-same:01M7D281MFHHWHGMXR1TBECTQM":45},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7D281MFHHWHGMXR1TBECTQM","test-tagging",null,"Classifies existing tests by standard traits and reports their distribution. USE FOR: tagging all tests with category attributes, categorizing\u002Ftagging\u002F labeling each test, compare happy vs error paths, audit the test mix, describe coverage shape by test type, or tag then verify the project builds. Read bodies when names mislead. Apply canonical attributes; otherwise report only. DO NOT USE FOR: requests owned by test-anti-patterns, coverage-analysis, crap-score, test-gap-analysis, code-testing-agent, or migration skills.","itsmejay18\u002FAI-Skills-for-My-Development-Stack","itsmejay18","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F167779943?v=4","01M7CZRFC6DDZA5V2CX8WDSZED","Jay Jemino Ababon ","01M7CZRFCVRNW1SFHSQXEJ3CQN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F13-Testing-QA\u002Ftest-tagging\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: test-tagging\ndescription: >\n  Classifies existing tests by standard traits and reports their distribution.\n  USE FOR: tagging all tests with category attributes, categorizing\u002Ftagging\u002F\n  labeling each\n  test, compare happy vs error paths, audit the test mix, describe coverage shape\n  by test type, or tag then verify the project builds. Read bodies when names\n  mislead. Apply canonical attributes; otherwise report only. DO NOT USE FOR:\n  requests owned by test-anti-patterns, coverage-analysis, crap-score,\n  test-gap-analysis, code-testing-agent, or migration skills.\nlicense: MIT\n---\n\n# Test Trait Tagging\n\nAnalyze an existing test suite in any supported language and apply a standardized set of trait tags to each test method, giving teams visibility into their test distribution (positive vs. negative, critical-path coverage, smoke tests, etc.).\n\n> **Language-specific guidance**: Try `test-analysis-extensions` once. If it is\n> unavailable, continue immediately with the built-in framework table below;\n> never block tagging on the helper.\n\n## When to Use\n\n- Auditing a test project to understand the mix of test types\n- Adding trait attributes to untagged tests\n- Generating a summary report of trait distribution across a test suite\n- Reviewing whether critical paths have sufficient coverage\n\n## When Not to Use\n\n- Writing new tests from scratch (use `code-testing-agent` for any language, or `writing-mstest-tests` for MSTest)\n- Running or filtering tests (use `run-tests` for .NET; equivalent native runners elsewhere)\n- Migrating between test frameworks\n- General quality, smell, flakiness, or assertion audits (use `test-anti-patterns` or the matching analysis skill)\n- Diagnostic .NET executed line\u002Fbranch\u002FCobertura interpretation or project-wide CRAP risk (use `coverage-analysis`); raw coverage collection (use `run-tests` for .NET, native tooling otherwise)\n- CRAP analysis for a named method, class, or file (use `crap-score`)\n- Behavioral gaps where a test would survive broken production logic (use `test-gap-analysis`)\n\n## Inputs\n\n| Input | Required | Description |\n|-------|----------|-------------|\n| Test project or files | No | Path to the test project, folder, or specific test files. Discover from the current workspace when omitted. |\n| Scope | No | `tag` (apply canonical attributes, or a confirmed project convention), `audit` (report only), or `both` (default: `both`). Frameworks declared `report-only` always emit a report; `convention-based` frameworks edit only after the user confirms the convention. |\n| Framework | No | Auto-detected. Override when detection fails. |\n\n## Trait Taxonomy\n\nUse exactly these trait names and values. Do not invent new trait values outside this table.\n\n| Trait Value | Meaning | Heuristics |\n|-------------|---------|------------|\n| `positive` | Verifies expected behavior under normal\u002Fvalid conditions | Asserts success, valid output, expected state, no exceptions for valid input |\n| `negative` | Verifies correct handling of invalid input, errors, or edge cases | Asserts exceptions, error codes, validation failures, rejects bad input |\n| `boundary` | Tests limits, thresholds, empty\u002Fnull\u002FNone\u002Fnil inputs, min\u002Fmax values | Operates on `0`, `-1`, `int.MaxValue` \u002F `sys.maxsize` \u002F `Number.MAX_SAFE_INTEGER` \u002F `math.MaxInt64` \u002F `i32::MAX`, empty string, null\u002FNone\u002Fnil\u002Fundefined, empty collection, boundary of valid range |\n| `critical-path` | Core workflow that must never break; breakage blocks users | Tests the primary success scenario of a key public API or user-facing feature |\n| `smoke` | Quick sanity check that the system is operational | Fast, no complex setup, verifies basic wiring (e.g., service resolves, endpoint returns 200) |\n| `regression` | Reproduces a specific previously-reported bug | References a bug ID, issue number, or describes a fix in its name or comments |\n| `integration` | Crosses process, network, or persistence boundaries | Uses real database, HTTP client, file system, external service, or multi-component setup |\n| `end-to-end` | Full user workflow spanning the entire application stack | Exercises a complete scenario from entry point to final result, distinct from single-boundary `integration` |\n| `performance` | Validates timing, throughput, or resource consumption | Asserts on elapsed time, memory, allocations, or uses benchmark harness (BenchmarkDotNet, pytest-benchmark, benchmark.js, JMH, `go test -bench`, criterion.rs, XCTMetric, kotlinx-benchmark, Google Benchmark) |\n| `security` | Verifies authentication, authorization, input sanitization, or secrets handling | Tests for SQL injection, XSS, CSRF, unauthorized access, token validation, permission checks |\n| `concurrency` | Validates thread safety, parallelism, or async correctness | Uses `Task.WhenAll` \u002F `Parallel.ForEach` \u002F `SemaphoreSlim` (.NET); `asyncio.gather` \u002F `threading.Lock` \u002F `multiprocessing` (Python); `Promise.all` \u002F worker threads (JS\u002FTS); `CompletableFuture` \u002F `ExecutorService` \u002F `synchronized` (Java); `go func` \u002F `sync.WaitGroup` \u002F `sync.Mutex` \u002F `chan` (Go); `Mutex` \u002F `Thread.new` (Ruby); `tokio::spawn` \u002F `Arc\u003CMutex\u003C_>>` \u002F `crossbeam` (Rust); `DispatchQueue` \u002F `actor` (Swift); `coroutineScope` \u002F `Mutex` (Kotlin); `Start-Job` \u002F `RunspacePool` (PowerShell); `std::thread` \u002F `std::mutex` (C++); reproduces race conditions |\n| `resilience` | Tests retry logic, timeouts, circuit breakers, or graceful degradation | Asserts behavior under transient failures, network drops, or service unavailability (e.g., Polly, tenacity, p-retry, resilience4j, hystrix, opossum, retry-go) |\n| `destructive` | Mutates shared or external state that is hard to roll back | Deletes records, drops resources, modifies global config -- useful for CI isolation decisions |\n| `configuration` | Verifies settings loading, defaults, environment behavior | Tests missing config keys, invalid values, environment variable fallbacks, options validation |\n| `flaky` | Known to intermittently fail (meta-tag for test health tracking) | Mark tests the team knows are unreliable; used to quarantine or prioritize stabilization |\n\nA single test may have **multiple traits** (e.g., both `negative` and `boundary`). At minimum, every test should receive one of `positive` or `negative`.\n\n## Workflow\n\n### Step 1: Detect the language, framework, and tagging capability\n\nResolve the requested test scope from the current workspace before asking for a\npath. The skill context's `Base directory` contains these instructions, not the\nuser's repository. Always inspect the current working directory before claiming\nthat repository files are unavailable. If the prompt's relative path is absent,\nsearch the workspace for the named project\u002Ffile and retry the exact result. A\nsuccessful search proves that the target is present; if the normal reader then\nreports that same path missing, treat the contradiction as a reader\npath-normalization or transport failure rather than asking the user for files.\nUse a shell text reader (`sed`\u002F`cat` on Unix,\n`Get-Content` on PowerShell) only for a confirmed reader availability,\ntransport, or path-normalization failure and only after verifying the canonical\npath remains inside the current workspace. Stop on content-exclusion,\npermission\u002Fpolicy, workspace-boundary, or unknown read failures. Never ask the\nuser for a path or file contents after a workspace search found a readable\ntarget.\n\nFor an `auto-edit` framework, a failed patch\u002Feditor call is not a stopping\ncondition only when the failure is confirmed tool availability, transport, or\npath normalization. Do not bypass stale-context, concurrent-change,\npermission\u002Fpolicy, or path-boundary errors. Before a shell fallback, resolve\nthe canonical path inside the current workspace, freshly read the file, and use\nan anchored transformation that aborts unless the expected old text and exact\nmatch count are unchanged. Then re-open the complete file, inspect the diff,\nand run Step 6 validation. Do not report proposed attributes as completion when\nthe user asked to apply them.\n\nIdentify the language and framework. Try the matching\n`test-analysis-extensions` guidance once. If unavailable, classify capability\nfrom the built-in rules below:\n\n- **`auto-edit`** — framework has canonical tag syntax this skill can safely insert (.NET `[TestCategory]` \u002F `[Trait]` \u002F `[Category]` \u002F `[Property]`, pytest `@pytest.mark.\u003Cname>`, JUnit 5 `@Tag(\"...\")`, TestNG `groups = {\"...\"}`, RSpec metadata `it \"...\" , :tag => true`, Pester `-Tag '...'`, Kotest `@Tags(...)`, Swift Testing `@Tag(.tagName)`, Catch2 `[tag]`, doctest `* doctest::test_suite(\"tag\")` decorator).\n- **`report-only`** — framework has no canonical, agreed-upon tag attribute; report tags in a Markdown table only and do not edit source (Go standard `testing` without build-tag conventions, Jest\u002FVitest without consistent describe-prefix convention, Rust without project-specific cfg conventions, XCTest without a test plan, GoogleTest without test-name prefix conventions, Mocha without describe-prefix conventions).\n- **`convention-based`** — framework uses naming or file conventions for tagging (Go `\u002F\u002Fgo:build integration` build tags, file-name suffixes like `*_integration_test.go`, GoogleTest `INTEGRATION_*` filter prefix). Only emit canonical edits when the user has confirmed the project convention; otherwise treat as `report-only`.\n\nCapture the capability before Step 4.\n\n### Step 2: Scan existing traits\n\nCheck which tests already have trait attributes. Use the extension when loaded;\notherwise use this built-in table as the source of truth:\n\n| Framework | Existing Attribute | Example |\n|-----------|--------------------|---------|\n| MSTest | `[TestCategory(\"...\")]` | `[TestCategory(\"positive\")]` |\n| xUnit | `[Trait(\"Category\", \"...\")]` | `[Trait(\"Category\", \"positive\")]` |\n| NUnit | `[Category(\"...\")]` | `[Category(\"positive\")]` |\n| TUnit | `[Property(\"Category\", \"...\")]` | `[Property(\"Category\", \"positive\")]` |\n| JUnit 5 | `@Tag(\"...\")` | `@Tag(\"positive\")` |\n| TestNG | `@Test(groups = {\"...\"})` | `@Test(groups = {\"positive\"})` |\n| pytest | `@pytest.mark.\u003Cname>` | `@pytest.mark.positive` |\n| RSpec | metadata after `it` | `it \"...\", :positive do` |\n| Pester | `-Tag '...'` | `It '...' -Tag 'positive'` |\n| Kotest | `@Tags(...)` | `@Tags(Positive)` |\n| Swift Testing | `@Tag(.\u003Cname>)` | `@Test(.tags(.positive))` |\n| Catch2 | `[tag]` in name | `TEST_CASE(\"...\", \"[positive]\")` |\n| doctest | `* doctest::test_suite(\"...\")` decorator | `TEST_CASE(\"...\" *doctest::test_suite(\"positive\"))` |\n\nRecord which tests already have tags to avoid duplication.\n\n### Step 3: Classify each test method\n\nBuild one canonical inventory containing each discovered test exactly once.\nRecord the test identifier, behavioral classification, and traits in that\ninventory; use the same rows for source edits, per-test reporting, totals, and\ndistribution counts. Do not hand-count a separate denominator. Before\npublishing, reconcile the reported total with the number of inventory rows and\nverify that every row contributes to each displayed trait count.\n\nFor each test method without traits, analyze:\n\n1. **Method name** -- names containing `Invalid`, `Fail`, `Error`, `Throw`, `Reject`, `BadInput`, `Null`, `None`, `Nil`, `Negative`, `raises_`, `_throws_`, `_returns_error` suggest `negative`\n2. **Assertion type** -- `Assert.ThrowsException` \u002F `Assert.Throws` \u002F `Should().Throw()` \u002F `pytest.raises` \u002F `expect(fn).toThrow` \u002F `assertThrows` \u002F `assert.Error(t, err)` \u002F `expect { ... }.to raise_error` \u002F `#[should_panic]` \u002F `XCTAssertThrowsError` \u002F `Should -Throw` \u002F `EXPECT_THROW` suggest `negative`\n3. **Input values** -- `null` \u002F `None` \u002F `nil` \u002F `undefined`, `\"\"`, `0`, `-1`, `int.MaxValue` \u002F `sys.maxsize` \u002F `Number.MAX_SAFE_INTEGER` \u002F `math.MaxInt64` \u002F `i32::MAX`, empty collections suggest `boundary`\n4. **Setup complexity** -- minimal setup with basic assertions suggests `smoke`; external dependencies (file\u002Fdb\u002Fnet\u002Fenv) suggest `integration`\n5. **Comments and names** -- references to issue numbers or \"regression\" \u002F \"bug\" \u002F \"fix for #...\" suggest `regression`\n6. **Timing assertions** -- `Stopwatch`, `BenchmarkDotNet`, elapsed-time checks; pytest-benchmark fixtures; benchmark.js; JMH `@Benchmark`; `go test -bench`; criterion.rs; XCTMetric; Google Benchmark; kotlinx-benchmark suggest `performance`\n7. **Feature centrality** -- tests on primary public API entry points or critical user workflows suggest `critical-path`\n8. **Security patterns** -- validates auth, checks permissions, sanitizes input, tests for injection, handles tokens\u002Fsecrets suggest `security`\n9. **Parallel\u002Fasync constructs** -- per-language concurrency primitives (see Trait Taxonomy table) suggest `concurrency`\n10. **Fault injection** -- simulates failures, tests retries, timeouts, or circuit breakers suggest `resilience`\n11. **State mutation** -- deletes external records, drops resources, modifies shared\u002Fglobal state suggest `destructive`\n12. **Full-stack flow** -- test spans entry point through data layer to final response, covering a complete user scenario suggest `end-to-end`\n13. **Config\u002Fsettings** -- loads configuration, tests missing keys, validates options, checks environment variables suggest `configuration`\n14. **Known instability** -- test has skip \u002F ignore annotations with comments about flakiness, or names contain \"flaky\" \u002F \"intermittent\" suggest `flaky`\n15. **Default** -- if the test verifies a normal success path, tag `positive`\n\nWhen in doubt between `positive` and `negative`, read the assertion: if it asserts success -> `positive`; if it asserts failure -> `negative`.\n\nFor a requested distribution or coverage-shape audit, use available production\ncode to map each test to the exact outcome it exercises before summarizing.\nCall out duplicated boundary coverage and whether the test inventory represents\nboth sides of named thresholds and the observable collaborator outcomes on\nbusiness-critical paths. Keep these as concise distribution observations, not\nnew trait values. Do not perform mutation reasoning, prescribe new tests, or\nexpand into the behavioral-gap audit owned by `test-gap-analysis`.\n\n### Step 4: Apply trait attributes (or report only)\n\n**If the resolved capability is `auto-edit`**, add the appropriate attribute to\neach test method. Place trait attributes adjacent to the existing test\nattribute. Examples:\n\nApply traits at the individual test-method\u002Fcase level. Do not substitute one\nclass-level category for method-level classification: different methods usually\nexercise different positive, negative, and boundary behavior.\n\n**MSTest:**\n```csharp\n[TestMethod]\n[TestCategory(\"negative\")]\n[TestCategory(\"boundary\")]\npublic void Parse_NullInput_ThrowsArgumentNullException() { ... }\n```\n\n**xUnit:**\n```csharp\n[Fact]\n[Trait(\"Category\", \"positive\")]\n[Trait(\"Category\", \"critical-path\")]\npublic void CreateOrder_ValidItems_ReturnsConfirmation() { ... }\n```\n\n**NUnit:**\n```csharp\n[Test]\n[Category(\"regression\")]\n[Category(\"negative\")]\npublic void Calculate_OverflowInput_ReturnsError() \u002F\u002F Fix for #1234\n{ ... }\n```\n\n**pytest:**\n```python\n@pytest.mark.negative\n@pytest.mark.boundary\ndef test_parse_none_input_raises_value_error():\n    ...\n```\n\n**JUnit 5:**\n```java\n@Test\n@Tag(\"positive\")\n@Tag(\"critical-path\")\nvoid createOrder_validItems_returnsConfirmation() { ... }\n```\n\n**TestNG:**\n```java\n@Test(groups = {\"negative\", \"boundary\"})\npublic void parse_nullInput_throwsIllegalArgumentException() { ... }\n```\n\n**RSpec:**\n```ruby\nit \"rejects null input\", :negative, :boundary do\n  ...\nend\n```\n\n**Pester:**\n```powershell\nIt 'Rejects null input' -Tag 'negative','boundary' {\n    ...\n}\n```\n\n**Kotest:**\n```kotlin\n@Tags(Negative, Boundary)\nclass ParserSpec : StringSpec({\n    \"rejects null input\" { ... }\n})\n```\n\n**Swift Testing:**\n```swift\n@Test(.tags(.negative, .boundary))\nfunc parseNullInputThrows() throws { ... }\n```\n\n**Catch2:**\n```cpp\nTEST_CASE(\"Parse null input throws\", \"[negative][boundary]\") { ... }\n```\n\n**If the resolved capability is `report-only`** (Go standard `testing`, plain\nJest\u002FVitest without convention, Rust without project-specific cfg, plain\nXCTest, plain GoogleTest, plain Mocha), do NOT modify source files. Instead emit\na concise mapping from each test to its suggested tags. Recommend a project-wide\nconvention only when the user asks how to persist or filter those tags; an\nanalysis-only request should report and stop.\n\n**If the resolved capability is `convention-based`** (e.g., Go\n`\u002F\u002Fgo:build integration`, `*_integration_test.go`, GoogleTest `INTEGRATION_*`\nprefix), only emit canonical edits when the user has confirmed the project's\nconvention. Otherwise treat as `report-only`.\n\n### Step 5: Generate trait summary\n\nAfter tagging, produce a summary table. Include only traits with a non-zero\ncount unless the user asks for the full taxonomy; zero-filled rows obscure the\nsuite's actual shape. For a small report-only suite, keep the per-test mapping\nand non-zero distribution together rather than expanding into a dashboard.\n\n```\n## Trait Distribution\n\n| Trait         | Count | % of Total |\n|---------------|-------|------------|\n| positive      |    50 |      64.1% |\n| negative      |    28 |      35.9% |\n| boundary      |     8 |      10.3% |\n| critical-path |    12 |      15.4% |\n| **Total tests** | **78** | -- |\n\nNote: Percentages exceed 100% because tests can have multiple traits.\n```\n\nInclude observations such as:\n- Ratio of positive to negative tests\n- Whether critical-path tests exist for key public APIs\n- Any tests that could not be confidently classified (list them for manual review)\n\n`boundary` and every other specialized trait are additive. A boundary success\ncase still counts as `positive`; a rejected boundary still counts as `negative`.\nDerive the positive\u002Fnegative distribution after applying this rule.\n\n### Step 6: Verify edits before reporting\n\nFor every `auto-edit` framework, run the narrowest command that compiles the\nedited attributes and confirms test discovery. This is required even when the\nuser asks only to add tags: syntactically plausible attributes are not a\ncompleted edit.\n\n| Framework | Minimum verification |\n|---|---|\n| .NET | Run `dotnet build \u003Ctest-project>`, then confirm discovery with `dotnet test \u003Ctest-project> --list-tests --no-build`. Do not execute the suite unless the user asks; route execution to `run-tests`. |\n| pytest | collect the edited suite with the repository's configured pytest command |\n| JUnit\u002FTestNG | compile tests through the repository's Maven\u002FGradle test task |\n| Other auto-edit frameworks | Use the repository's narrowest compile or test-discovery command |\n\nIf an edit or patch application was uncertain, re-open the complete edited file\nbefore verification and reconcile every inventory row with the actual\nattribute next to that test. Do not report success from a partial diff or from\nthe intended patch. If verification fails, report the exact command and error;\nnever publish a successful distribution handoff for uncompiled edits.\n\n## Validation\n\n- [ ] Every test method has at least one trait classification (`positive` or `negative` at minimum) — in the report for `report-only` frameworks, or as an attribute for `auto-edit` frameworks\n- [ ] The total equals the per-test inventory count, and displayed trait counts were derived from that inventory\n- [ ] No invented trait values outside the taxonomy table\n- [ ] Existing trait attributes were preserved, not duplicated\n- [ ] The trait summary table was generated\n- [ ] For `auto-edit` frameworks, the project still builds \u002F tests still discover without executing unrequested tests (`dotnet build` plus list mode \u002F `pytest --collect-only` \u002F `mvn test-compile` \u002F `go vet .\u002F...` \u002F `cargo check --tests` \u002F `npm run test:list` \u002F equivalent)\n- [ ] The final summary cites successful validation commands and the discovered test count when a discovery command is available\n- [ ] For `report-only` frameworks, no source files were modified\n- [ ] For `convention-based` frameworks, edits were applied ONLY when a project convention was confirmed\n\n## Common Pitfalls\n\n| Pitfall | Solution |\n|---------|----------|\n| Guessing traits without reading the test body | Always read assertions and setup to classify accurately |\n| Tagging a test only as `boundary` without `positive`\u002F`negative` | Every test should also be `positive` or `negative` -- `boundary` is additive |\n| Using the wrong attribute syntax for the detected framework | Match the loaded extension or built-in table (don't put `[TestCategory]` in xUnit or `@pytest.mark.x` in unittest) |\n| Duplicating an existing category attribute | Check for pre-existing traits in Step 2 before adding |\n| Over-tagging as `critical-path` | Reserve for tests on primary public entry points, not every helper |\n| Editing Go \u002F plain Jest \u002F plain Rust \u002F plain XCTest \u002F plain GoogleTest source | These are `report-only` by default — emit a Markdown table instead. Only edit if the user confirms a project-wide convention (build tag, file suffix, describe-prefix, test-plan grouping). |\n| Inventing tag prefixes for convention-based frameworks | Confirm the project's existing convention before adopting one — don't guess between `_integration_test.go`, `\u002F\u002Fgo:build integration`, or `IntegrationTest` prefix |\n| Missing language-specific concurrency \u002F async primitives | Use the loaded extension when available; otherwise use the Trait Taxonomy concurrency row |\n","# Test Trait Tagging\n\nAnalyze an existing test suite in any supported language and apply a standardized set of trait tags to each test method, giving teams visibility into their test distribution (positive vs. negative, critical-path coverage, smoke tests, etc.).\n\n> **Language-specific guidance**: Try `test-analysis-extensions` once. If it is\n> unavailable, continue immediately with the built-in framework table below;\n> never block tagging on the helper.\n\n## When to Use\n\n- Auditing a test project to understand the mix of test types\n- Adding trait attributes to untagged tests\n- Generating a summary report of trait distribution across a test suite\n- Reviewing whether critical paths have sufficient coverage\n\n## When Not to Use\n\n- Writing new tests from scratch (use `code-testing-agent` for any language, or `writing-mstest-tests` for MSTest)\n- Running or filtering tests (use `run-tests` for .NET; equivalent native runners elsewhere)\n- Migrating between test frameworks\n- General quality, smell, flakiness, or assertion audits (use `test-anti-patterns` or the matching analysis skill)\n- Diagnostic .NET executed line\u002Fbranch\u002FCobertura interpretation or project-wide CRAP risk (use `coverage-analysis`); raw coverage collection (use `run-tests` for .NET, native tooling otherwise)\n- CRAP analysis for a named method, class, or file (use `crap-score`)\n- Behavioral gaps where a test would survive broken production logic (use `test-gap-analysis`)\n\n## Inputs\n\n| Input | Required | Description |\n|-------|----------|-------------|\n| Test project or files | No | Path to the test project, folder, or specific test files. Discover from the current workspace when omitted. |\n| Scope | No | `tag` (apply canonical attributes, or a confirmed project convention), `audit` (report only), or `both` (default: `both`). Frameworks declared `report-only` always emit a report; `convention-based` frameworks edit only after the user confirms the convention. |\n| Framework | No | Auto-detected. Override when detection fails. |\n\n## Trait Taxonomy\n\nUse exactly these trait names and values. Do not invent new trait values outside this table.\n\n| Trait Value | Meaning | Heuristics |\n|-------------|---------|------------|\n| `positive` | Verifies expected behavior under normal\u002Fvalid conditions | Asserts success, valid output, expected state, no exceptions for valid input |\n| `negative` | Verifies correct handling of invalid input, errors, or edge cases | Asserts exceptions, error codes, validation failures, rejects bad input |\n| `boundary` | Tests limits, thresholds, empty\u002Fnull\u002FNone\u002Fnil inputs, min\u002Fmax values | Operates on `0`, `-1`, `int.MaxValue` \u002F `sys.maxsize` \u002F `Number.MAX_SAFE_INTEGER` \u002F `math.MaxInt64` \u002F `i32::MAX`, empty string, null\u002FNone\u002Fnil\u002Fundefined, empty collection, boundary of valid range |\n| `critical-path` | Core workflow that must never break; breakage blocks users | Tests the primary success scenario of a key public API or user-facing feature |\n| `smoke` | Quick sanity check that the system is operational | Fast, no complex setup, verifies basic wiring (e.g., service resolves, endpoint returns 200) |\n| `regression` | Reproduces a specific previously-reported bug | References a bug ID, issue number, or describes a fix in its name or comments |\n| `integration` | Crosses process, network, or persistence boundaries | Uses real database, HTTP client, file system, external service, or multi-component setup |\n| `end-to-end` | Full user workflow spanning the entire application stack | Exercises a complete scenario from entry point to final result, distinct from single-boundary `integration` |\n| `performance` | Validates timing, throughput, or resource consumption | Asserts on elapsed time, memory, allocations, or uses benchmark harness (BenchmarkDotNet, pytest-benchmark, benchmark.js, JMH, `go test -bench`, criterion.rs, XCTMetric, kotlinx-benchmark, Google Benchmark) |\n| `security` | Verifies authentication, authorization, input sanitization, or secrets handling | Tests for SQL injection, XSS, CSRF, unauthorized access, token validation, permission checks |\n| `concurrency` | Validates thread safety, parallelism, or async correctness | Uses `Task.WhenAll` \u002F `Parallel.ForEach` \u002F `SemaphoreSlim` (.NET); `asyncio.gather` \u002F `threading.Lock` \u002F `multiprocessing` (Python); `Promise.all` \u002F worker threads (JS\u002FTS); `CompletableFuture` \u002F `ExecutorService` \u002F `synchronized` (Java); `go func` \u002F `sync.WaitGroup` \u002F `sync.Mutex` \u002F `chan` (Go); `Mutex` \u002F `Thread.new` (Ruby); `tokio::spawn` \u002F `Arc\u003CMutex\u003C_>>` \u002F `crossbeam` (Rust); `DispatchQueue` \u002F `actor` (Swift); `coroutineScope` \u002F `Mutex` (Kotlin); `Start-Job` \u002F `RunspacePool` (PowerShell); `std::thread` \u002F `std::mutex` (C++); reproduces race conditions |\n| `resilience` | Tests retry logic, timeouts, circuit breakers, or graceful degradation | Asserts behavior under transient failures, network drops, or service unavailability (e.g., Polly, tenacity, p-retry, resilience4j, hystrix, opossum, retry-go) |\n| `destructive` | Mutates shared or external state that is hard to roll back | Deletes records, drops resources, modifies global config -- useful for CI isolation decisions |\n| `configuration` | Verifies settings loading, defaults, environment behavior | Tests missing config keys, invalid values, environment variable fallbacks, options validation |\n| `flaky` | Known to intermittently fail (meta-tag for test health tracking) | Mark tests the team knows are unreliable; used to quarantine or prioritize stabilization |\n\nA single test may have **multiple traits** (e.g., both `negative` and `boundary`). At minimum, every test should receive one of `positive` or `negative`.\n\n## Workflow\n\n### Step 1: Detect the language, framework, and tagging capability\n\nResolve the requested test scope from the current workspace before asking for a\npath. The skill context's `Base directory` contains these instructions, not the\nuser's repository. Always inspect the current working directory before claiming\nthat repository files are unavailable. If the prompt's relative path is absent,\nsearch the workspace for the named project\u002Ffile and retry the exact result. A\nsuccessful search proves that the target is present; if the normal reader then\nreports that same path missing, treat the contradiction as a reader\npath-normalization or transport failure rather than asking the user for files.\nUse a shell text reader (`sed`\u002F`cat` on Unix,\n`Get-Content` on PowerShell) only for a confirmed reader availability,\ntransport, or path-normalization failure and only after verifying the canonical\npath remains inside the current workspace. Stop on content-exclusion,\npermission\u002Fpolicy, workspace-boundary, or unknown read failures. Never ask the\nuser for a path or file contents after a workspace search found a readable\ntarget.\n\nFor an `auto-edit` framework, a failed patch\u002Feditor call is not a stopping\ncondition only when the failure is confirmed tool availability, transport, or\npath normalization. Do not bypass stale-context, concurrent-change,\npermission\u002Fpolicy, or path-boundary errors. Before a shell fallback, resolve\nthe canonical path inside the current workspace, freshly read the file, and use\nan anchored transformation that aborts unless the expected old text and exact\nmatch count are unchanged. Then re-open the complete file, inspect the diff,\nand run Step 6 validation. Do not report proposed attributes as completion when\nthe user asked to apply them.\n\nIdentify the language and framework. Try the matching\n`test-analysis-extensions` guidance once. If unavailable, classify capability\nfrom the built-in rules below:\n\n- **`auto-edit`** — framework has canonical tag syntax this skill can safely insert (.NET `[TestCategory]` \u002F `[Trait]` \u002F `[Category]` \u002F `[Property]`, pytest `@pytest.mark.\u003Cname>`, JUnit 5 `@Tag(\"...\")`, TestNG `groups = {\"...\"}`, RSpec metadata `it \"...\" , :tag => true`, Pester `-Tag '...'`, Kotest `@Tags(...)`, Swift Testing `@Tag(.tagName)`, Catch2 `[tag]`, doctest `* doctest::test_suite(\"tag\")` decorator).\n- **`report-only`** — framework has no canonical, agreed-upon tag attribute; report tags in a Markdown table only and do not edit source (Go standard `testing` without build-tag conventions, Jest\u002FVitest without consistent describe-prefix convention, Rust without project-specific cfg conventions, XCTest without a test plan, GoogleTest without test-name prefix conventions, Mocha without describe-prefix conventions).\n- **`convention-based`** — framework uses naming or file conventions for tagging (Go `\u002F\u002Fgo:build integration` build tags, file-name suffixes like `*_integration_test.go`, GoogleTest `INTEGRATION_*` filter prefix). Only emit canonical edits when the user has confirmed the project convention; otherwise treat as `report-only`.\n\nCapture the capability before Step 4.\n\n### Step 2: Scan existing traits\n\nCheck which tests already have trait attributes. Use the extension when loaded;\notherwise use this built-in table as the source of truth:\n\n| Framework | Existing Attribute | Example |\n|-----------|--------------------|---------|\n| MSTest | `[TestCategory(\"...\")]` | `[TestCategory(\"positive\")]` |\n| xUnit | `[Trait(\"Category\", \"...\")]` | `[Trait(\"Category\", \"positive\")]` |\n| NUnit | `[Category(\"...\")]` | `[Category(\"positive\")]` |\n| TUnit | `[Property(\"Category\", \"...\")]` | `[Property(\"Category\", \"positive\")]` |\n| JUnit 5 | `@Tag(\"...\")` | `@Tag(\"positive\")` |\n| TestNG | `@Test(groups = {\"...\"})` | `@Test(groups = {\"positive\"})` |\n| pytest | `@pytest.mark.\u003Cname>` | `@pytest.mark.positive` |\n| RSpec | metadata after `it` | `it \"...\", :positive do` |\n| Pester | `-Tag '...'` | `It '...' -Tag 'positive'` |\n| Kotest | `@Tags(...)` | `@Tags(Positive)` |\n| Swift Testing | `@Tag(.\u003Cname>)` | `@Test(.tags(.positive))` |\n| Catch2 | `[tag]` in name | `TEST_CASE(\"...\", \"[positive]\")` |\n| doctest | `* doctest::test_suite(\"...\")` decorator | `TEST_CASE(\"...\" *doctest::test_suite(\"positive\"))` |\n\nRecord which tests already have tags to avoid duplication.\n\n### Step 3: Classify each test method\n\nBuild one canonical inventory containing each discovered test exactly once.\nRecord the test identifier, behavioral classification, and traits in that\ninventory; use the same rows for source edits, per-test reporting, totals, and\ndistribution counts. Do not hand-count a separate denominator. Before\npublishing, reconcile the reported total with the number of inventory rows and\nverify that every row contributes to each displayed trait count.\n\nFor each test method without traits, analyze:\n\n1. **Method name** -- names containing `Invalid`, `Fail`, `Error`, `Throw`, `Reject`, `BadInput`, `Null`, `None`, `Nil`, `Negative`, `raises_`, `_throws_`, `_returns_error` suggest `negative`\n2. **Assertion type** -- `Assert.ThrowsException` \u002F `Assert.Throws` \u002F `Should().Throw()` \u002F `pytest.raises` \u002F `expect(fn).toThrow` \u002F `assertThrows` \u002F `assert.Error(t, err)` \u002F `expect { ... }.to raise_error` \u002F `#[should_panic]` \u002F `XCTAssertThrowsError` \u002F `Should -Throw` \u002F `EXPECT_THROW` suggest `negative`\n3. **Input values** -- `null` \u002F `None` \u002F `nil` \u002F `undefined`, `\"\"`, `0`, `-1`, `int.MaxValue` \u002F `sys.maxsize` \u002F `Number.MAX_SAFE_INTEGER` \u002F `math.MaxInt64` \u002F `i32::MAX`, empty collections suggest `boundary`\n4. **Setup complexity** -- minimal setup with basic assertions suggests `smoke`; external dependencies (file\u002Fdb\u002Fnet\u002Fenv) suggest `integration`\n5. **Comments and names** -- references to issue numbers or \"regression\" \u002F \"bug\" \u002F \"fix for #...\" suggest `regression`\n6. **Timing assertions** -- `Stopwatch`, `BenchmarkDotNet`, elapsed-time checks; pytest-benchmark fixtures; benchmark.js; JMH `@Benchmark`; `go test -bench`; criterion.rs; XCTMetric; Google Benchmark; kotlinx-benchmark suggest `performance`\n7. **Feature centrality** -- tests on primary public API entry points or critical user workflows suggest `critical-path`\n8. **Security patterns** -- validates auth, checks permissions, sanitizes input, tests for injection, handles tokens\u002Fsecrets suggest `security`\n9. **Parallel\u002Fasync constructs** -- per-language concurrency primitives (see Trait Taxonomy table) suggest `concurrency`\n10. **Fault injection** -- simulates failures, tests retries, timeouts, or circuit breakers suggest `resilience`\n11. **State mutation** -- deletes external records, drops resources, modifies shared\u002Fglobal state suggest `destructive`\n12. **Full-stack flow** -- test spans entry point through data layer to final response, covering a complete user scenario suggest `end-to-end`\n13. **Config\u002Fsettings** -- loads configuration, tests missing keys, validates options, checks environment variables suggest `configuration`\n14. **Known instability** -- test has skip \u002F ignore annotations with comments about flakiness, or names contain \"flaky\" \u002F \"intermittent\" suggest `flaky`\n15. **Default** -- if the test verifies a normal success path, tag `positive`\n\nWhen in doubt between `positive` and `negative`, read the assertion: if it asserts success -> `positive`; if it asserts failure -> `negative`.\n\nFor a requested distribution or coverage-shape audit, use available production\ncode to map each test to the exact outcome it exercises before summarizing.\nCall out duplicated boundary coverage and whether the test inventory represents\nboth sides of named thresholds and the observable collaborator outcomes on\nbusiness-critical paths. Keep these as concise distribution observations, not\nnew trait values. Do not perform mutation reasoning, prescribe new tests, or\nexpand into the behavioral-gap audit owned by `test-gap-analysis`.\n\n### Step 4: Apply trait attributes (or report only)\n\n**If the resolved capability is `auto-edit`**, add the appropriate attribute to\neach test method. Place trait attributes adjacent to the existing test\nattribute. Examples:\n\nApply traits at the individual test-method\u002Fcase level. Do not substitute one\nclass-level category for method-level classification: different methods usually\nexercise different positive, negative, and boundary behavior.\n\n**MSTest:**\n```csharp\n[TestMethod]\n[TestCategory(\"negative\")]\n[TestCategory(\"boundary\")]\npublic void Parse_NullInput_ThrowsArgumentNullException() { ... }\n```\n\n**xUnit:**\n```csharp\n[Fact]\n[Trait(\"Category\", \"positive\")]\n[Trait(\"Category\", \"critical-path\")]\npublic void CreateOrder_ValidItems_ReturnsConfirmation() { ... }\n```\n\n**NUnit:**\n```csharp\n[Test]\n[Category(\"regression\")]\n[Category(\"negative\")]\npublic void Calculate_OverflowInput_ReturnsError() \u002F\u002F Fix for #1234\n{ ... }\n```\n\n**pytest:**\n```python\n@pytest.mark.negative\n@pytest.mark.boundary\ndef test_parse_none_input_raises_value_error():\n    ...\n```\n\n**JUnit 5:**\n```java\n@Test\n@Tag(\"positive\")\n@Tag(\"critical-path\")\nvoid createOrder_validItems_returnsConfirmation() { ... }\n```\n\n**TestNG:**\n```java\n@Test(groups = {\"negative\", \"boundary\"})\npublic void parse_nullInput_throwsIllegalArgumentException() { ... }\n```\n\n**RSpec:**\n```ruby\nit \"rejects null input\", :negative, :boundary do\n  ...\nend\n```\n\n**Pester:**\n```powershell\nIt 'Rejects null input' -Tag 'negative','boundary' {\n    ...\n}\n```\n\n**Kotest:**\n```kotlin\n@Tags(Negative, Boundary)\nclass ParserSpec : StringSpec({\n    \"rejects null input\" { ... }\n})\n```\n\n**Swift Testing:**\n```swift\n@Test(.tags(.negative, .boundary))\nfunc parseNullInputThrows() throws { ... }\n```\n\n**Catch2:**\n```cpp\nTEST_CASE(\"Parse null input throws\", \"[negative][boundary]\") { ... }\n```\n\n**If the resolved capability is `report-only`** (Go standard `testing`, plain\nJest\u002FVitest without convention, Rust without project-specific cfg, plain\nXCTest, plain GoogleTest, plain Mocha), do NOT modify source files. Instead emit\na concise mapping from each test to its suggested tags. Recommend a project-wide\nconvention only when the user asks how to persist or filter those tags; an\nanalysis-only request should report and stop.\n\n**If the resolved capability is `convention-based`** (e.g., Go\n`\u002F\u002Fgo:build integration`, `*_integration_test.go`, GoogleTest `INTEGRATION_*`\nprefix), only emit canonical edits when the user has confirmed the project's\nconvention. Otherwise treat as `report-only`.\n\n### Step 5: Generate trait summary\n\nAfter tagging, produce a summary table. Include only traits with a non-zero\ncount unless the user asks for the full taxonomy; zero-filled rows obscure the\nsuite's actual shape. For a small report-only suite, keep the per-test mapping\nand non-zero distribution together rather than expanding into a dashboard.\n\n```\n## Trait Distribution\n\n| Trait         | Count | % of Total |\n|---------------|-------|------------|\n| positive      |    50 |      64.1% |\n| negative      |    28 |      35.9% |\n| boundary      |     8 |      10.3% |\n| critical-path |    12 |      15.4% |\n| **Total tests** | **78** | -- |\n\nNote: Percentages exceed 100% because tests can have multiple traits.\n```\n\nInclude observations such as:\n- Ratio of positive to negative tests\n- Whether critical-path tests exist for key public APIs\n- Any tests that could not be confidently classified (list them for manual review)\n\n`boundary` and every other specialized trait are additive. A boundary success\ncase still counts as `positive`; a rejected boundary still counts as `negative`.\nDerive the positive\u002Fnegative distribution after applying this rule.\n\n### Step 6: Verify edits before reporting\n\nFor every `auto-edit` framework, run the narrowest command that compiles the\nedited attributes and confirms test discovery. This is required even when the\nuser asks only to add tags: syntactically plausible attributes are not a\ncompleted edit.\n\n| Framework | Minimum verification |\n|---|---|\n| .NET | Run `dotnet build \u003Ctest-project>`, then confirm discovery with `dotnet test \u003Ctest-project> --list-tests --no-build`. Do not execute the suite unless the user asks; route execution to `run-tests`. |\n| pytest | collect the edited suite with the repository's configured pytest command |\n| JUnit\u002FTestNG | compile tests through the repository's Maven\u002FGradle test task |\n| Other auto-edit frameworks | Use the repository's narrowest compile or test-discovery command |\n\nIf an edit or patch application was uncertain, re-open the complete edited file\nbefore verification and reconcile every inventory row with the actual\nattribute next to that test. Do not report success from a partial diff or from\nthe intended patch. If verification fails, report the exact command and error;\nnever publish a successful distribution handoff for uncompiled edits.\n\n## Validation\n\n- [ ] Every test method has at least one trait classification (`positive` or `negative` at minimum) — in the report for `report-only` frameworks, or as an attribute for `auto-edit` frameworks\n- [ ] The total equals the per-test inventory count, and displayed trait counts were derived from that inventory\n- [ ] No invented trait values outside the taxonomy table\n- [ ] Existing trait attributes were preserved, not duplicated\n- [ ] The trait summary table was generated\n- [ ] For `auto-edit` frameworks, the project still builds \u002F tests still discover without executing unrequested tests (`dotnet build` plus list mode \u002F `pytest --collect-only` \u002F `mvn test-compile` \u002F `go vet .\u002F...` \u002F `cargo check --tests` \u002F `npm run test:list` \u002F equivalent)\n- [ ] The final summary cites successful validation commands and the discovered test count when a discovery command is available\n- [ ] For `report-only` frameworks, no source files were modified\n- [ ] For `convention-based` frameworks, edits were applied ONLY when a project convention was confirmed\n\n## Common Pitfalls\n\n| Pitfall | Solution |\n|---------|----------|\n| Guessing traits without reading the test body | Always read assertions and setup to classify accurately |\n| Tagging a test only as `boundary` without `positive`\u002F`negative` | Every test should also be `positive` or `negative` -- `boundary` is additive |\n| Using the wrong attribute syntax for the detected framework | Match the loaded extension or built-in table (don't put `[TestCategory]` in xUnit or `@pytest.mark.x` in unittest) |\n| Duplicating an existing category attribute | Check for pre-existing traits in Step 2 before adding |\n| Over-tagging as `critical-path` | Reserve for tests on primary public entry points, not every helper |\n| Editing Go \u002F plain Jest \u002F plain Rust \u002F plain XCTest \u002F plain GoogleTest source | These are `report-only` by default — emit a Markdown table instead. Only edit if the user confirms a project-wide convention (build tag, file suffix, describe-prefix, test-plan grouping). |\n| Inventing tag prefixes for convention-based frameworks | Confirm the project's existing convention before adopting one — don't guess between `_integration_test.go`, `\u002F\u002Fgo:build integration`, or `IntegrationTest` prefix |\n| Missing language-specific concurrency \u002F async primitives | Use the loaded extension when available; otherwise use the Trait Taxonomy concurrency row |\n",{"name":5,"license":15,"description":24},"Classifies existing tests by standard traits and reports their distribution. USE FOR: tagging all tests with category attributes, categorizing\u002Ftagging\u002F labeling each test, compare happy vs error paths, audit the test mix, describe coverage shape by test type, or tag then verify the project builds. Read bodies when names mislead. Apply canonical attributes; otherwise report only. DO NOT USE FOR: requests owned by test-anti-patterns, coverage-analysis, crap-score, test-gap-analysis, code-testing-agent, or migration skills.\n","main","30954af1dcd1a74b63f05deb2e2c41e5ecae4a82","13-Testing-QA\u002Ftest-tagging","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack","https:\u002F\u002Fgithub.com\u002Fitsmejay18","2026-09-18 16:06:36",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill test-tagging",{"tool":37,"command":38},"bunx","bunx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill test-tagging",{"tool":40,"command":41},"pnpm","pnpm dlx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill test-tagging","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F13-Testing-QA\u002Ftest-tagging\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7D2RKBHPZ3E1RNN5DWHT550","vectorization","Design, implement, optimize, and review SIMD code in .NET. USE FOR: vectorizing scalar loops with TensorPrimitives, Vector64\u002F128\u002F256\u002F512, or platform hardware intrinsics; reviewing existing SIMD code, including Vector\u003CT>, for contract equivalence, tail handling, memory safety, portability, fallbacks, and measured performance. DO NOT USE FOR: performance work unrelated to SIMD or vectorization.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fvectorization\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7D2RDJ7RN3QK8GJR0QTER1D","resolve-project-references","Guide for interpreting ResolveProjectReferences time in MSBuild performance summaries. Activate when ResolveProjectReferences appears as the most expensive target and developers are trying to optimize it directly. Explains that the reported time includes wait time for dependent project builds and is misleading. Guides users to focus on task self-time instead. Do not activate for general build performance -- use build-perf-diagnostics instead.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fresolve-project-references\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7D2R1H2GTNZYHG9YRX3JDQW","optimizing-ef-core-queries","Optimize and improve the performance of slow Entity Framework Core (EF Core) queries: make them generate less SQL, make fewer database round-trips, and return results faster. Use whenever an EF Core or DbContext query or data-access path is slow or should be made faster — whether or not EF Core owns the database schema. For EF Core, not Dapper or raw ADO.NET.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Foptimizing-ef-core-queries\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7D2QREG04W1YT0NEBHEW5C9","microbenchmarking","Activate this skill when BenchmarkDotNet (BDN) is involved in the task — creating, running, configuring, or reviewing BDN benchmarks. Also activate when microbenchmarking .NET code would be useful and BenchmarkDotNet is the likely tool. Consider activating when answering a .NET performance question requires measurement and BenchmarkDotNet may be needed. Covers microbenchmark design, BDN configuration and project setup, how to run BDN microbenchmarks efficiently and effectively, and using BDN for side-by-side performance comparisons. Do NOT use for profiling\u002Ftracing .NET code (dotnet-trace, PerfView), production telemetry, or load\u002Fstress testing (Crank, k6).","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fmicrobenchmarking\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7D2QGE175XWPZVACVH2868Z","incremental-build","Guide for optimizing MSBuild incremental builds. USE FOR: builds slower than expected on subsequent runs, 'nothing changed but it rebuilds anyway', diagnosing why targets re-execute unnecessarily, fixing broken no-op builds. Covers 8 common causes: missing Inputs\u002FOutputs on custom targets, volatile properties in output paths (timestamps\u002FGUIDs), file writes outside tracked Outputs, missing FileWrites registration, glob changes, Visual Studio Fast Up-to-Date Check (FUTDC) issues. Key diagnostic: look for 'Building target completely' vs 'Skipping target' in binlog. DO NOT USE FOR: first-time build slowness (use build-perf-baseline), parallelism issues (use build-parallelism), evaluation-phase slowness (use eval-performance), non-MSBuild build systems.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fincremental-build\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7D2Q1DQTC6K49R73WQTTPSB","eval-performance","Guide for diagnosing and improving MSBuild project evaluation performance. USE FOR: builds slow before any compilation starts, high evaluation time in binlog analysis, expensive glob patterns walking large directories (node_modules, .git, bin\u002Fobj), deep import chains (>20 levels), preprocessed output >10K lines indicating heavy evaluation, property functions with file I\u002FO ($([System.IO.File]::ReadAllText(...))), multiple evaluations per project. Covers the 5 MSBuild evaluation phases, glob optimization via DefaultItemExcludes, import chain analysis with \u002Fpp preprocessing. DO NOT USE FOR: compilation-time slowness (use build-perf-diagnostics), incremental build issues (use incremental-build), non-MSBuild build systems.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Feval-performance\u002FSKILL.md",[],[]]