cosmos-provider

Name: Cosmos Provider
Author: VSadov

// Implementation details for the EF Core Azure Cosmos DB provider. Use when changing Cosmos-specific code.

Manus에서 실행

$ git log --oneline --stat

stars:0

forks:0

updated:2026년 3월 14일 05:12

SKILL.md

readonly

name	cosmos-provider
description	Implementation details for the EF Core Azure Cosmos DB provider. Use when changing Cosmos-specific code.
user-invocable	false

Cosmos DB Provider

Non-relational provider with its own parallel query pipeline. Uses JSON for document materialization.

When to Use

Working on Cosmos SQL generation
Working on document storage, partition key configuration, or CosmosClientWrapper

Key Differences from Relational

No migrations — use EnsureCreated()
Documents as JSON — owned and complex types become embedded objects
Partition key configuration required for performance
ETag for optimistic concurrency
No cross-container joins

related-skills.json

같은 저장소

make-skill.md

from "VSadov/dotnet"

Create new Agent Skills for GitHub Copilot. Use when asked to create, scaffold, or add a skill. Generates SKILL.md with frontmatter, directory structure, and optional resources.

2026-03-140

multithreaded-task-migration.md

from "VSadov/dotnet"

Guide for migrating MSBuild tasks to multithreaded mode support, including compatibility red-team review. Use this when converting tasks to thread-safe versions, implementing IMultiThreadableTask, adding TaskEnvironment support, or auditing migrations for behavioral compatibility.

2026-03-100

changewaves.md

from "VSadov/dotnet"

Manage MSBuild Change Waves: create new waves, condition features behind opt-out flags, write tests for wave-gated features, document change waves in ChangeWaves.md, and retire expired waves. Use when adding changes that need an opt-out or rotating out old change waves. Changes that introduce a user-visible behavior change should consider whether to use a changewave.

2026-02-270

ci-analysis.md

from "VSadov/dotnet"

Analyze CI build and test status from Azure DevOps and Helix for dotnet repository PRs. Use when checking CI status, investigating failures, determining if a PR is ready to merge, or given URLs containing dev.azure.com or helix.dot.net. Also use when asked "why is CI red", "test failures", "retry CI", "rerun tests", "is CI green", "build failed", "checks failing", or "flaky tests".

2026-02-250

review-council.md

from "VSadov/dotnet"

Multi-agent review council. Invoke for: review council, fellowship review, multi-agent review, panel review, diverse model review.

2026-02-190

package.json