vnext

Use when adding query parameter filters to a monitor list endpoint. Covers the 3-class pattern (FilterInput / FilterDescriptor / Filter), bracket-notation binding with [eq]/[contains] operators, conflict validation, type-discriminated 400 validation, and in-memory LINQ apply — all derived from the component filter implementation.

Scope is repo-wide domain knowledge (not bound to a single workspace). vNext Runtime platform referansı. Workflow, state, transition, task, schema, view, function ve extension kavramlarını, JSON tanım yapılarını ve C# mapping/rule pattern'lerini kapsar. vNext bileşenleri oluşturulurken veya düzenlenirken bu skill'i kullanın. Trigger this skill whenever vNext workflow/task/schema/view/function/extension JSON or `.csx` mapping/rule files are being created or edited anywhere in the monorepo (or in target vnext domain repositories).

Creates a structured English GitHub issue using gh CLI based on a user-provided scope description. Translates the scope to English, optionally scans the codebase to enrich the technical description, shows the draft for user approval, then opens the issue. Use when the user asks to open an issue, create a GitHub issue, report a bug/task/feature, or says "issue aç", "issue oluştur", or "scan project" / "projeyi tara".

Creates an English GitHub Pull Request using gh CLI by analyzing commits on the current branch compared to the base branch. Generates a structured PR title and body, shows it for user approval, then creates the PR. Use when the user asks to create a PR, open a pull request, push and create PR, or mentions "gh pr", "pull request", or "open PR".

Generates a Conventional Commits-style English commit message by analyzing staged git changes. Use when the user asks for a commit message, wants to commit changes, mentions "commit", "git commit", or asks for help writing a commit message.

Generate or update vNext platform documentation for the vnext-docs Docusaurus site. Use when the user says "döküman oluştur", "create docs", "document this feature", or asks to update/sync documentation after a code change.

Generates a comprehensive matrix report from vnext-meta JSON files. Outputs a markdown table showing features, deprecations, known issues, components, and limits by version. Use when the user says "meta matrix", "meta rapor", "feature matrix", "meta ozet", or "meta tablo".

Validates vnext-meta package JSON files for schema compliance, version consistency, and codebase alignment. Use when the user says "validate meta", "meta check", "meta kontrol", "vnext-meta validate", or after modifying vnext-meta JSON files.

Systematic code review for vNext workflow pipeline changes. Checks pipeline step discipline, repository include efficiency, long-polling correctness, error boundary integrity, result pattern compliance, and clean architecture. Use when the user says "code review", "review et", "incele", "review yap", or asks to review pipeline, transition, or workflow code.

Generates a comprehensive matrix report from vnext-meta JSON files. Outputs a markdown table showing features, deprecations, known issues, components, and limits by version. Use when the user says 'meta matrix', 'meta rapor', 'feature matrix', 'meta ozet', or 'meta tablo'.

Validates vnext-meta package JSON files for schema compliance, version consistency, and codebase alignment. Use when the user says 'validate meta', 'meta check', 'meta kontrol', 'vnext-meta validate', or after modifying vnext-meta JSON files.

Creates a structured English GitHub issue using gh CLI based on a user-provided scope description. Translates the scope to English, optionally scans the codebase to enrich the technical description, shows the draft for user approval, then opens the issue. Use when the user asks to open an issue, create a GitHub issue, report a bug/task/feature, or says "issue aç", "issue oluştur", or "scan project" / "projeyi tara".

Generate or update vNext platform documentation for the vnext-docs Docusaurus site. Use when the user says "döküman oluştur", "create docs", "document this feature", or asks to update/sync documentation after a code change.

Systematic code review for vNext workflow pipeline changes. Checks pipeline step discipline, repository include efficiency, long-polling correctness, error boundary integrity, result pattern compliance, and clean architecture. Use when the user says "code review", "review et", "incele", "review yap", or asks to review pipeline, transition, or workflow code.