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: Source Control
Apply MCAF source-control guidance for repository structure, branch naming, merge strategy, commit hygiene, and secrets-in-git discipline. USE FOR: bootstrapping source-control policy; tightening branch, merge, or PR rules; documenting commit or release hygiene. DO NOT USE FOR: CI/CD workflow design with no source-control policy change; one-off git commands that do not alter repo policy. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
Trigger On
- bootstrapping source-control policy
- tightening branch, merge, or PR rules
- documenting commit or release hygiene
- dealing with secrets-in-git or repository structure issues
Workflow
- Agree on merge and release strategy before scaling implementation.
- Keep branch and PR rules explicit in-repo.
- Treat secrets in git history as a critical incident, not cleanup noise.
- Use concrete policy language, not hand-waving.
Deliver
- clear branch and merge strategy
- updated contribution or governance docs
- safer repository hygiene around commits, PRs, and secrets
Validate
- naming and merge rules are explicit
- release/versioning implications are documented where needed
- secret hygiene is treated as policy, not tribal knowledge
Load References
- read references/source-control.md first
- open references/naming-branches.md only when the task is specifically about branch naming
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.