What problem does it solve? Teams working across multiple repositories often drift into inconsistent branching models, messy commit histories, and uneven code review practices. This Skill enforces a single, machine-readable contribution workflow so changelogs, release notes, and triage tooling work without manual curation. ## Core Features & Use Cases - Branching model: Two protected long-lived branches (main for production, dev for staging) plus short-lived typed feature branches cut from dev, with a documented hotfix path. - Conventional Commits & PR standards: Strict commit message format, PR templates, sizing rules (< 400 LOC), review SLAs, and merge strategies per target branch. - Pre-commit gates & repo bootstrapping: Shared lint, format, type-check, and test gates for Python, TypeScript, Go, and Terraform, plus ready-to-copy assets (CODEOWNERS, PR template, branch protection settings) for new repos. - Use Case: When starting a new feature, ask the assistant to cut a properly named branch from dev, write a compliant commit, and open a PR with the standard template — all following MIS rules automatically. ## Quick Start Ask the assistant to create a new feature branch from dev and open a pull request following the MIS contribution workflow.
