dotnet-testing-filesystem-testing-abstractions
bykevintsengtw· 30 skills
使用 System.IO.Abstractions 測試檔案系統操作的專門技能。當需要測試 File、Directory、Path 等操作、模擬檔案系統時使用。涵蓋 IFileSystem、MockFileSystem、檔案讀寫測試、目錄操作測試等。 Make sure to use this skill whenever the user mentions file system testing, IFileSystem, MockFileSystem, System.IO.Abstractions, or testing file/directory operations, even if they don't explicitly ask for filesystem testing guidance. Keywords: file testing, filesystem, 檔案測試, 檔案系統測試, IFileSystem, MockFileSystem, System.IO.Abstractions, File.ReadAllText, File.WriteAllText, Directory.CreateDirectory, Path.Combine, mock file system, 檔案抽象化
How to install dotnet-testing-filesystem-testing-abstractions?
kevintsengtw/dotnet-testing-agent-skills/dotnet-testing-filesystem-testing-abstractions
$npx -y skills add kevintsengtw/dotnet-testing-agent-skills --skill dotnet-testing-filesystem-testing-abstractionsInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/kevintsengtw/dotnet-testing-agent-skills" --skill "kevintsengtw/dotnet-testing-agent-skills/dotnet-testing-filesystem-testing-abstractions"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/kevintsengtw/dotnet-testing-agent-skills" that are relevant to the current task. Run `npx skills add "https://github.com/kevintsengtw/dotnet-testing-agent-skills"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- tddTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.Jul 2026
- test-driven-developmentUse when implementing any feature or bugfix, before writing implementation codeJul 2026
- qaInteractive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues.Jul 2026
- verification-before-completionUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output…Jul 2026
- webapp-testingToolkit for interacting with and testing local web applications using Playwright.Jul 2026
- playwright-best-practicesUse when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking…Jul 2026
