Use when contributing to the mcpp project — submitting bug fixes, new features, code optimizations, documentation improvements, or any PR. Covers issue creation, branch conventions, build verification, CI requirements, and PR workflow using gh and git.
Use when writing or editing anything under docs/ (English or 简体中文), README files, or long-form design records — states the register mcpp documentation is written in (declarative, precise, professional), the constructions that are not admitted (question headings, conversational asides, internet slang, figurative…
Use when releasing a new version of mcpp — bumps version, creates tag, triggers release CI, and monitors until all platforms succeed. Covers the full release checklist to avoid common pitfalls like version string mismatches.
A development process for changes in the repository, dividing work into bug fixes, optimisations, and new features. New features require prior issue discussion and a written design in .agents/docs, followed by testing, validation, continuous integration, and pull-request checks.
A guide for finding the cause of failed or crashing mbun runtime tests, including single-file test runs, debugger backtraces, and source-code tracing by API.