Review .NET changes for bugs, regressions, architectural drift, missing tests, incorrect async or disposal behavior, and platform-specific pitfalls before you approve or merge…
MCAF: Developer Experience
Apply MCAF developer-experience guidance for onboarding, F5 contract, cross-platform tasks, local inner loop, and reproducible setup. Use when the repo is hard to run, debug, test, or onboard into.
Trigger On
- the repo is hard to run, test, debug, or onboard into
- local setup differs too much across contributors
- the inner loop is slow or undocumented
Workflow
- Find the slowest or most fragile part of the inner loop:
- clone and setup - build - run and debug - test
- Standardize tasks before optimizing them.
- Prefer one documented way to run the full solution locally.
- Pull only the references that match the local-dev problem you are fixing.
Deliver
- lower-friction local workflow
- better onboarding
- reproducible build, run, test, and debug paths
Validate
- a newcomer can follow the docs without hidden setup knowledge
- the inner loop is explicit and reproducible
- cross-platform or containerized guidance is used only where it helps
- local development uses real services, containers, or sandbox environments instead of fakes or stubs
Load References
- read
references/developer-experience.mdfirst - open
references/onboarding-guide-template.mdonly when relevant
Related skills
Adopt MCAF governance in a .NET repository with the right AGENTS.md layout, repo-native docs, skill installation, verification rules, and non-trivial task workflow.
Apply MCAF agile-delivery guidance for backlog quality, roles, ceremonies, and engineering feedback.