devskill 2.0.6 → 2.0.8

package/skills/create-tldr-page/SKILL.md

@@ -0,0 +1,210 @@
+---
+name: create-tldr-page
+description: 'Create a tldr page from documentation URLs and command examples, requiring both URL and command name.'
+---
+
+# Create TLDR Page
+
+## Overview
+
+You are an expert technical documentation specialist who creates concise, actionable `tldr` pages
+following the tldr-pages project standards. Your task is to transform verbose documentation into
+clear, example-driven command references.
+
+## Objectives
+
+1. **Require both URL and command** - If either is missing, provide helpful guidance to obtain them
+2. **Extract key examples** - Identify the most common and useful command patterns
+3. **Follow tldr format strictly** - Use the template structure with proper markdown formatting
+4. **Validate documentation source** - Ensure the URL points to authoritative upstream documentation
+
+## Prompt Parameters
+
+### Required
+
+* **Command** - The name of the command or tool (e.g., `git`, `nmcli`, `distrobox-create`)
+* **URL** - Link to authoritative upstream documentation
+  - If one or more URLs are passed without a preceding `#fetch`, apply #tool:fetch to the first URL
+  - If ${file} is provided in lieu of a URL, and ${file} has a relevant URL to **command**, then use
+  the data from the file as if fetched from the URL; use the URL extracted from the file when
+  creating the `tldr` page
+    - If more than one URL is in the file, prompt for which URL should be used for the `tldr` page
+
+### Optional
+
+* **Context files** - Additional documentation or examples
+* **Search data** - Results from documentation searches
+* **Text data** - Raw text from manual pages or help output
+* **Help output** - Raw data matching `-h`, `--help`, `/?`, `--tldr`, `--man`, etc.
+
+> [!IMPORTANT]
+> If a help argument (like `--help` or `--tldr`) is passed, provide a summary of THIS prompt,
+rendering the output as markdown using the tldr template format. Do NOT create a new tldr page for
+the command.
+
+## Usage
+
+### Syntax
+
+```bash
+/create-tldr-page #fetch <URL> <command> [text data] [context file]
+```
+
+### Error Handling
+
+#### Missing Command
+
+**User**
+
+```bash
+/create-tldr-page https://some-command.io/docs/manual.html
+```
+
+**Agent**
+
+```text
+I'll fetch the URL and analyze the documentation.
+From the data extracted, I assume the command is `some-command`. Is this correct? (yes/no)
+```
+
+#### Missing URL
+
+**User**
+
+```bash
+/create-tldr-page some-command
+```
+
+**Agent**
+
+```text
+A URL to authoritative documentation is required for tldr pages. Here are some acceptable URL
+patterns:
+
+1. https://gnu.org/software/manual/html_node/some-command.html
+2. https://some.org/serve/some.man.html#some-command
+3. https://some-command.io/docs/cli/latest/manual
+4. https://some-command.io/docs/quickstart
+
+Please provide the documentation URL for `some-command`.
+```
+
+## Template
+
+Use this template structure when creating tldr pages:
+
+```markdown
+# command
+
+> Short, snappy description.
+> Some subcommands such as `subcommand1` have their own usage documentation.
+> More information: <https://url-to-upstream.tld>.
+
+- View documentation for creating something:
+
+`tldr command-subcommand1`
+
+- View documentation for managing something:
+
+`tldr command-subcommand2`
+```
+
+### Template Guidelines
+
+- **Title**: Use exact command name (lowercase)
+- **Description**: One-line summary of what the command does
+- **Subcommands note**: Only include if relevant
+- **More information**: Link to authoritative upstream documentation (required)
+- **Examples**: 5-8 most common use cases, ordered by frequency of use
+- **Placeholders**: Use `{{placeholder}}` syntax for user-provided values
+
+## Examples
+
+### Reference Examples
+
+You MAY fetch these example tldr pages to understand the proper format and style:
+
+* [git](https://raw.githubusercontent.com/jhauga/tldr/refs/heads/main/pages/common/git.md)
+* [distrobox-create](https://raw.githubusercontent.com/jhauga/tldr/refs/heads/main/pages/linux/distrobox-create.md)
+* [nmcli](https://raw.githubusercontent.com/jhauga/tldr/refs/heads/main/pages/linux/nmcli.md)
+
+### Expected Output Using Example
+
+**User**
+
+```bash
+/create-tldr-page #fetch https://git-scm.com/docs/git git
+```
+
+**Agent**
+
+````markdown
+# git
+
+> Distributed version control system.
+> Some subcommands such as `commit`, `add`, `branch`, `switch`, `push`, etc. have their own usage documentation.
+> More information: <https://git-scm.com/docs/git>.
+
+- Create an empty Git repository:
+
+`git init`
+
+- Clone a remote Git repository from the internet:
+
+`git clone {{https://example.com/repo.git}}`
+
+- View the status of the local repository:
+
+`git status`
+
+- Stage all changes for a commit:
+
+`git add {{[-A|--all]}}`
+
+- Commit changes to version history:
+
+`git commit {{[-m|--message]}} {{message_text}}`
+
+- Push local commits to a remote repository:
+
+`git push`
+
+- Pull any changes made to a remote:
+
+`git pull`
+
+- Reset everything the way it was in the latest commit:
+
+`git reset --hard; git clean {{[-f|--force]}}`
+````
+
+### Output Formatting Rules
+
+You MUST follow these placeholder conventions:
+
+- **Options with arguments**: When an option takes an argument, wrap BOTH the option AND its argument separately
+  - Example: `minipro {{[-p|--device]}} {{chip_name}}`
+  - Example: `git commit {{[-m|--message]}} {{message_text}}`
+  - **DO NOT** combine them as: `minipro -p {{chip_name}}` (incorrect)
+
+- **Options without arguments**: Wrap standalone options (flags) that don't take arguments
+  - Example: `minipro {{[-E|--erase]}}`
+  - Example: `git add {{[-A|--all]}}`
+
+- **Single short options**: Do NOT wrap single short options when used alone without long form
+  - Example: `ls -l` (not wrapped)
+  - Example: `minipro -L` (not wrapped)
+  - However, if both short and long forms exist, wrap them: `{{[-l|--list]}}`
+
+- **Subcommands**: Generally do NOT wrap subcommands unless they are user-provided variables
+  - Example: `git init` (not wrapped)
+  - Example: `tldr {{command}}` (wrapped when variable)
+
+- **Arguments and operands**: Always wrap user-provided values
+  - Example: `{{device_name}}`, `{{chip_name}}`, `{{repository_url}}`
+  - Example: `{{path/to/file}}` for file paths
+  - Example: `{{https://example.com}}` for URLs
+
+- **Command structure**: Options should appear BEFORE their arguments in the placeholder syntax
+  - Correct: `command {{[-o|--option]}} {{value}}`
+  - Incorrect: `command -o {{value}}`

package/skills/create-tldr-page/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/create-tldr-page`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/creating-oracle-to-postgres-master-migration-plan/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/creating-oracle-to-postgres-master-migration-plan/SKILL.md

@@ -0,0 +1,83 @@
+---
+name: creating-oracle-to-postgres-master-migration-plan
+description: 'Discovers all projects in a .NET solution, classifies each for Oracle-to-PostgreSQL migration eligibility, and produces a persistent master migration plan. Use when starting a multi-project Oracle-to-PostgreSQL migration, creating a migration inventory, or assessing which .NET projects contain Oracle dependencies.'
+---
+
+# Creating an Oracle-to-PostgreSQL Master Migration Plan
+
+Analyze a .NET solution, classify every project for Oracle→PostgreSQL migration eligibility, and write a structured plan that downstream agents and skills can parse.
+
+## Workflow
+
+```
+Progress:
+- [ ] Step 1: Discover projects in the solution
+- [ ] Step 2: Classify each project
+- [ ] Step 3: Confirm with user
+- [ ] Step 4: Write the plan file
+```
+
+**Step 1: Discover projects**
+
+Find the Solution File (it has a `.sln` or `.slnx` extension) in the workspace root (ask the user if multiple exist). Parse it to extract all `.csproj` project references. For each project, note the name, path, and type (class library, web API, console, test, etc.).
+
+**Step 2: Classify each project**
+
+Scan every non-test project for Oracle indicators:
+
+- NuGet references: `Oracle.ManagedDataAccess`, `Oracle.EntityFrameworkCore` (check `.csproj` and `packages.config`)
+- Config entries: Oracle connection strings in `appsettings.json`, `web.config`, `app.config`
+- Code usage: `OracleConnection`, `OracleCommand`, `OracleDataReader`
+- DDL cross-references under `.github/oracle-to-postgres-migration/DDL/Oracle/` (if present)
+
+Assign one classification per project:
+
+| Classification | Meaning |
+|---|---|
+| **MIGRATE** | Has Oracle interactions requiring conversion |
+| **SKIP** | No Oracle indicators (UI-only, shared utility, etc.) |
+| **ALREADY_MIGRATED** | A `-postgres` or `.Postgres` duplicate exists and appears processed |
+| **TEST_PROJECT** | Test project; handled by the testing workflow |
+
+**Step 3: Confirm with user**
+
+Present the classified list. Let the user adjust classifications or migration ordering before finalizing.
+
+**Step 4: Write the plan file**
+
+Save to: `.github/oracle-to-postgres-migration/Reports/Master Migration Plan.md`
+
+Use this exact template — downstream consumers depend on the structure:
+
+````markdown
+# Master Migration Plan
+
+**Solution:** {solution file name}
+**Solution Root:** {REPOSITORY_ROOT}
+**Created:** {timestamp}
+**Last Updated:** {timestamp}
+
+## Solution Summary
+
+| Metric | Count |
+|--------|-------|
+| Total projects in solution | {n} |
+| Projects requiring migration | {n} |
+| Projects already migrated | {n} |
+| Projects skipped (no Oracle usage) | {n} |
+| Test projects (handled separately) | {n} |
+
+## Project Inventory
+
+| # | Project Name | Path | Classification | Notes |
+|---|---|---|---|---|
+| 1 | {name} | {relative path} | MIGRATE | {notes} |
+| 2 | {name} | {relative path} | SKIP | No Oracle dependencies |
+
+## Migration Order
+
+1. **{ProjectName}** — {rationale, e.g., "Core data access library; other projects depend on it."}
+2. **{ProjectName}** — {rationale}
+````
+
+Order projects so that shared/foundational libraries are migrated before their dependents.

package/skills/creating-oracle-to-postgres-master-migration-plan/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/creating-oracle-to-postgres-master-migration-plan`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/creating-oracle-to-postgres-migration-bug-report/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/creating-oracle-to-postgres-migration-bug-report/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: creating-oracle-to-postgres-migration-bug-report
+description: 'Creates structured bug reports for defects found during Oracle-to-PostgreSQL migration. Use when documenting behavioral differences between Oracle and PostgreSQL as actionable bug reports with severity, root cause, and remediation steps.'
+---
+
+# Creating Bug Reports for Oracle-to-PostgreSQL Migration
+
+## When to Use
+
+- Documenting a defect caused by behavioral differences between Oracle and PostgreSQL
+- Writing or reviewing a bug report for an Oracle-to-PostgreSQL migration project
+
+## Bug Report Format
+
+Use the template in [references/BUG-REPORT-TEMPLATE.md](references/BUG-REPORT-TEMPLATE.md). Each report must include:
+
+- **Status**: ✅ RESOLVED, ⛔ UNRESOLVED, or ⏳ IN PROGRESS
+- **Component**: Affected endpoint, repository, or stored procedure
+- **Test**: Related automated test names
+- **Severity**: Low / Medium / High / Critical — based on impact scope
+- **Problem**: Expected Oracle behavior vs. observed PostgreSQL behavior
+- **Scenario**: Ordered reproduction steps with seed data, operation, expected result, and actual result
+- **Root Cause**: The specific Oracle/PostgreSQL behavioral difference causing the defect
+- **Solution**: Changes made or required, with explicit file paths
+- **Validation**: Steps to confirm the fix on both databases
+
+## Oracle-to-PostgreSQL Guidance
+
+- **Oracle is the source of truth** — frame expected behavior from the Oracle baseline
+- Call out data layer nuances explicitly: empty string vs. NULL, type coercion strictness, collation, sequence values, time zones, padding, constraints
+- Client code changes should be avoided unless required for correct behavior; when proposed, document and justify them clearly
+
+## Writing Style
+
+- Plain language, short sentences, clear next actions
+- Present or past tense consistently
+- Bullets and numbered lists for steps and validations
+- Minimal SQL excerpts and logs as evidence; omit sensitive data and keep snippets reproducible
+- Stick to existing runtime/language versions; avoid speculative fixes
+
+## Filename Convention
+
+Save bug reports as `BUG_REPORT_<DescriptiveSlug>.md` where `<DescriptiveSlug>` is a short PascalCase identifier (e.g., `EmptyStringNullHandling`, `RefCursorUnwrapFailure`).

package/skills/creating-oracle-to-postgres-migration-bug-report/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/creating-oracle-to-postgres-migration-bug-report`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/creating-oracle-to-postgres-migration-bug-report/references/BUG-REPORT-TEMPLATE.md

@@ -0,0 +1,79 @@
+# Bug Report Template
+
+Use this template when creating bug reports for Oracle-to-PostgreSQL migration defects.
+
+## Filename Format
+
+```
+BUG_REPORT_<DescriptiveSlug>.md
+```
+
+## Template Structure
+
+```markdown
+# Bug Report: <Title>
+
+**Status:** ✅ RESOLVED | ⛔ UNRESOLVED | ⏳ IN PROGRESS
+**Component:** <High-level component/endpoint and key method(s)>
+**Test:** <Related automated test names>
+**Severity:** Low | Medium | High | Critical
+
+---
+
+## Problem
+
+<Observable incorrect behavior. State expected behavior (Oracle baseline)
+versus actual behavior (PostgreSQL). Be specific and factual.>
+
+## Scenario
+
+<Ordered steps to reproduce the defect. Include:
+1. Prerequisites and seed data
+2. Exact operation or API call
+3. Expected result (Oracle)
+4. Actual result (PostgreSQL)>
+
+## Root Cause
+
+<Minimal, concrete technical cause. Reference the specific Oracle/PostgreSQL
+behavioral difference (e.g., empty string vs NULL, type coercion strictness).>
+
+## Solution
+
+<Changes made or required. Be explicit about data access layer changes,
+tracking flags, and any client code modifications. Note whether changes
+are already applied or still needed.>
+
+## Validation
+
+<Bullet list of passing tests or manual checks that confirm the fix:
+- Re-run reproduction steps on both Oracle and PostgreSQL
+- Compare row/column outputs
+- Check error handling parity>
+
+## Files Modified
+
+<Bullet list with relative file paths and short purpose for each change:
+- `src/DataAccess/FooRepository.cs` — Added explicit NULL check for empty string parameter>
+
+## Notes / Next Steps
+
+<Follow-ups, environment caveats, risks, or dependencies on other fixes.>
+```
+
+## Status Values
+
+| Status | Meaning |
+|--------|---------|
+| ✅ RESOLVED | Defect has been fixed and verified |
+| ⛔ UNRESOLVED | Defect has not been addressed yet |
+| ⏳ IN PROGRESS | Defect is being investigated or fix is underway |
+
+## Style Rules
+
+- Keep wording concise and factual
+- Use present or past tense consistently
+- Prefer bullets and numbered lists for steps and validation
+- Call out data layer nuances (tracking, padding, constraints) explicitly
+- Keep to existing runtime/language versions; avoid speculative fixes
+- Include minimal SQL excerpts and logs as evidence; omit sensitive data

package/skills/creating-oracle-to-postgres-migration-integration-tests/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/creating-oracle-to-postgres-migration-integration-tests/SKILL.md

@@ -0,0 +1,60 @@
+---
+name: creating-oracle-to-postgres-migration-integration-tests
+description: 'Creates integration test cases for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Generates DB-agnostic xUnit tests with deterministic seed data that validate behavior consistency across both database systems. Use when creating integration tests for a migrated project, generating test coverage for data access layers, or writing Oracle-to-PostgreSQL migration validation tests.'
+---
+
+# Creating Integration Tests for Oracle-to-PostgreSQL Migration
+
+Generates integration test cases for data access artifacts in a single target project. Tests validate behavior consistency when running against Oracle or PostgreSQL.
+
+## Prerequisites
+
+- The test project must already exist and compile (scaffolded separately).
+- Read the existing base test class and seed manager conventions before writing tests.
+
+## Workflow
+
+```
+Test Creation:
+- [ ] Step 1: Discover the test project conventions
+- [ ] Step 2: Identify testable data access artifacts
+- [ ] Step 3: Create seed data
+- [ ] Step 4: Write test cases
+- [ ] Step 5: Review determinism
+```
+
+**Step 1: Discover the test project conventions**
+
+Read the base test class, seed manager, and project file to understand inheritance patterns, transaction management, and seed file conventions.
+
+**Step 2: Identify testable data access artifacts**
+
+Scope to the target project only. List data access methods that interact with the database — repositories, DAOs, stored procedure callers, query builders.
+
+**Step 3: Create seed data**
+
+- Follow seed file location and naming conventions from the existing project.
+- Reuse existing seed files when possible.
+- Avoid `TRUNCATE TABLE` — keep existing database data intact.
+- Do not commit seed data; tests run in transactions that roll back.
+- Ensure seed data does not conflict with other tests.
+- Load and verify seed data before assertions depend on it.
+
+**Step 4: Write test cases**
+
+- Inherit from the base test class to get automatic transaction create/rollback.
+- Assert logical outputs (rows, columns, counts, error types), not platform-specific messages.
+- Assert specific expected values — never assert that a value is merely non-null or non-empty when a concrete value is available from seed data.
+- Avoid testing code paths that do not exist or asserting behavior that cannot occur.
+- Avoid redundant assertions across tests targeting the same method.
+
+**Step 5: Review determinism**
+
+Re-examine every assertion against non-null values. Confirm each is deterministic against the seeded data. Fix any assertion that depends on database state outside the test's control.
+
+## Key Constraints
+
+- **Oracle is the golden source** — tests capture Oracle's expected behavior.
+- **DB-agnostic assertions** — no platform-specific error messages or syntax in assertions.
+- **Seed only against Oracle** — test project will be migrated to PostgreSQL later.
+- **Scoped to one project** — do not create tests for artifacts outside the target project.

package/skills/creating-oracle-to-postgres-migration-integration-tests/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/creating-oracle-to-postgres-migration-integration-tests`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/csharp-async/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/csharp-async/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: csharp-async
+description: 'Get best practices for C# async programming'
+---
+
+# C# Async Programming Best Practices
+
+Your goal is to help me follow best practices for asynchronous programming in C#.
+
+## Naming Conventions
+
+- Use the 'Async' suffix for all async methods
+- Match method names with their synchronous counterparts when applicable (e.g., `GetDataAsync()` for `GetData()`)
+
+## Return Types
+
+- Return `Task<T>` when the method returns a value
+- Return `Task` when the method doesn't return a value
+- Consider `ValueTask<T>` for high-performance scenarios to reduce allocations
+- Avoid returning `void` for async methods except for event handlers
+
+## Exception Handling
+
+- Use try/catch blocks around await expressions
+- Avoid swallowing exceptions in async methods
+- Use `ConfigureAwait(false)` when appropriate to prevent deadlocks in library code
+- Propagate exceptions with `Task.FromException()` instead of throwing in async Task returning methods
+
+## Performance
+
+- Use `Task.WhenAll()` for parallel execution of multiple tasks
+- Use `Task.WhenAny()` for implementing timeouts or taking the first completed task
+- Avoid unnecessary async/await when simply passing through task results
+- Consider cancellation tokens for long-running operations
+
+## Common Pitfalls
+
+- Never use `.Wait()`, `.Result`, or `.GetAwaiter().GetResult()` in async code
+- Avoid mixing blocking and async code
+- Don't create async void methods (except for event handlers)
+- Always await Task-returning methods
+
+## Implementation Patterns
+
+- Implement the async command pattern for long-running operations
+- Use async streams (IAsyncEnumerable<T>) for processing sequences asynchronously
+- Consider the task-based asynchronous pattern (TAP) for public APIs
+
+When reviewing my C# code, identify these issues and suggest improvements that follow these best practices.

package/skills/csharp-async/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/csharp-async`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/csharp-docs/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.