Quality

.NET P/Invoke correctly calls native C/C++ libraries from .NET using DllImport and LibraryImport, covering signatures, strings, memory, SafeHandle, and cross-platform patterns. Use it for writing, reviewing, or debugging native interop code in .NET.

Optimizing EF Core Queries diagnoses and fixes slow Entity Framework Core queries by reducing generated SQL, database round-trips, and per-call translation cost. Use it when an EF Core query or data-access path is slow, emits N+1 statements, or pays LINQ translation overhead on every call.

Bug Detective provides a systematic debugging workflow for investigating and resolving code errors, exceptions, and failures. Use it when debugging, fixing errors, or troubleshooting broken code.

Code Review Excellence provides principles, checklists, and techniques for reviewing diffs and pull requests, writing actionable feedback, and establishing team review standards. Use it when auditing code quality, mentoring developers, or improving review cycles.

Daily Coding provides a quality assurance checklist for writing or modifying source code. Use it before, during, and after coding tasks to ensure minimal changes, type safety, security, and clean execution.

Guides debugging by creating external test scripts that replicate bugs, adding logs, and iterating until the issue is resolved. Suitable for isolating elusive bugs without internal mocking.

Guides composing PR titles and descriptions for the Fluid Framework repo, including two acceptable title styles and a body template with required sections.

Pipeline Test Triage analyzes Azure DevOps test failures for Fluid Framework pipeline runs. Use it to summarize failing tests, compare runs, separate flaky issues from real bugs, and identify when a bug should be filed.

Policy Check runs pnpm policy-check from the repo root to validate package compliance. Use it for a specific package with --path, or run the repository-wide check when changes may affect other packages.

Provides a structured approach to code review feedback: fetch comments, clarify requirements, implement one change at a time, run tests, and push. Emphasizes verification and quality over performative agreement.

Review checks a branch or diff for correctness, API compatibility, architecture, tests, performance, and security. Use it when you need a concise code review with optional deeper analysis.

Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior