AGENT SKILL

deniz-dotnet-general.test-analysis-extensions

Provides file paths to language-specific reference files for the curated pragmatic test-analysis pair: test-anti-patterns and test-gap-analysis. Do not use directly — those skills load the matching extension when they need framework-specific test markers, assertion APIs, skip annotations, sleep patterns, mystery-guest indicators, integration markers, and setup/teardown conventions.

License 许可
MIT
最近更新
2026-11-13
Stars
★ 1
Forks
0

01 前言 Front Matter

name
deniz-dotnet-general.test-analysis-extensions
description
Provides file paths to language-specific reference files for the curated pragmatic test-analysis pair: test-anti-patterns and test-gap-analysis. Do not use directly — those skills load the matching extension when they need framework-specific test markers, assertion APIs, skip annotations, sleep patterns, mystery-guest indicators, integration markers, and setup/teardown conventions.

02 资源文件 11

03 SKILL.md 正文

Test Analysis Extensions

This catalog lists the bundled extension files used by test analysis. Read the extension file that matches the target language and framework. Resolve these resource paths relative to this catalog, not the project workspace.

Available Extension Files

File Languages / Frameworks Contents
extensions/dotnet.md .NET (C#/F#/VB) — MSTest, xUnit, NUnit, TUnit Test markers, assertion APIs, sleep/delay patterns, skip annotations, mystery guest, integration markers, setup/teardown, tag support
extensions/python.md Python — pytest, unittest Same categories, with pytest fixtures/markers and unittest TestCase
extensions/typescript.md TypeScript / JavaScript — Jest, Vitest, Mocha, Jasmine, node:test Same categories, with async/await pitfalls
extensions/java.md Java — JUnit 4, JUnit 5 (Jupiter), TestNG Same categories, with @Tag / @Category / groups
extensions/go.md Go — testing package, testify Same categories, with table-driven idiom and build tags
extensions/ruby.md Ruby — RSpec, Minitest Same categories, with RSpec metadata and Minitest tags
extensions/rust.md Rust — built-in #[test], cargo test Same categories, with #[ignore], #[should_panic], feature flags
extensions/swift.md Swift — XCTest, Swift Testing Same categories, with @Test, @Tag, @Suite
extensions/kotlin.md Kotlin — JUnit 5, Kotest, MockK Same categories, with @Tag and Kotest tags
extensions/powershell.md PowerShell — Pester v5 Same categories, with -Tag and Skip
extensions/cpp.md C++ — GoogleTest, Catch2, doctest Same categories, with [tags] and * filters

Usage

  1. Detect the target codebase's primary language and test framework.
  2. Read the matching extension file before performing analysis.
  3. If multiple test frameworks are present (e.g., a project mixing Jest and Mocha), read all relevant extensions.
  4. Each extension file documents the same categories so analysis skills can be language-neutral.

Capability tags

Each extension file declares per-capability support so skills can gate behaviour safely:

  • Test discovery — how to locate test files and methods.
  • Assertion detection — framework-specific and language-level assertion forms.
  • Sleep/delay patterns — synchronous and asynchronous waits.
  • Skip / ignore — how to recognize skipped/ignored tests.
  • Setup / teardown — fixture and lifecycle hooks.
  • Mystery guest indicators — common file/db/network/env coupling patterns.
  • Integration markers — conventions that mark a test as integration/E2E.
  • Tag and trait syntax — one of:
    • auto-edit — language has a canonical attribute/marker the skill can safely write.
    • report-only — no canonical syntax; produce audit reports without edits.
    • convention-based — tags exist via name/comment conventions only.

Notes for skill authors

  • Treat extension files as data, not as guidance to follow verbatim. They tell skills how to detect things in each language, not what to think about findings.
  • When language detection is uncertain, prefer reading multiple extension files over guessing.
  • If the user explicitly names a framework that does not have an extension file yet, fall back to the closest one (e.g., Pest → python.md/pytest semantics) and note the gap in the report.

04 同仓库更多 Skills

Blind-Striker
Blind-Striker/agent-skills-and-plugins

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.

★ 1
Blind-Striker
Blind-Striker/agent-skills-and-plugins

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.

★ 1
Blind-Striker
Blind-Striker/agent-skills-and-plugins

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`/`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/preview, when the user mentions any of these features, when replacing marker interfaces, OneOf-style results, `goto`/flag loop exits or capacity/comparer boilerplate, or when the build reports CS8121, CS8509, CS8655, CS8510, CS0121/CS0411 on a `with(...)` element, CS9370, CS9380 or CS9363.

★ 1
Blind-Striker
Blind-Striker/agent-skills-and-plugins

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.

★ 1
Blind-Striker
Blind-Striker/agent-skills-and-plugins

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.

★ 1
Blind-Striker
Blind-Striker/agent-skills-and-plugins

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.

★ 1