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: Documentation
Apply MCAF documentation guidance for docs structure, navigation, source-of-truth placement, and writing quality. Use when a repo’s docs are missing, stale, duplicated, or hard to navigate, or when adding new durable engineering guidance.
Trigger On
- docs are missing, stale, duplicated, or hard to navigate
- a repo needs a cleaner source-of-truth structure
- durable engineering guidance needs to be added without bloating pages
Workflow
- Decide the canonical location for each fact before writing.
- Prefer navigational docs that link to detail instead of copying detail.
- Keep bootstrap pages small; move workflow scaffolds into skills.
- Update stale docs in the same change as the code or policy they describe.
Deliver
- cleaner docs structure
- better source-of-truth placement
- docs that reflect the code and workflow that actually exist
Validate
- each durable fact has one clear home
- entry pages route the reader correctly
- pages do not bloat with template or reference dumps
- docs match the real repo, not the intended future repo
Load References
- read
references/documentation.mdfor structure and documentation-quality guidance
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.