JasonXuDeveloper/EasyEcs

audit-docs

Audit the EasyEcs docs (docs/content en+zh, README, rules file, samples) for stale API names, wrong or non-exemplary examples, missing best practices, duplication and en/zh drift. Use after code changes land and before merging to master.

Idioma del texto original: inglés

audit-core

Audit src/EasyEcs.Core for redundant designs, duplicated logic, coupling, bugs and hot-path cost, and fix what is proven. Use for a core review round or before a release.

Idioma del texto original: inglés

audit-generator

Audit the EasyEcs source generators (ArityGenerator, ComponentGenerator, SystemGenerator) for generator speed, incremental-generator best practices, caching, and use of newer Roslyn features such as interceptors. Use when changing a generator or reviewing…

Idioma del texto original: inglés

audit-naming

Audit EasyEcs names (public Core API, generated members, analyzer descriptors, internals) for ambiguity, wrong meaning, ECS convention and consistency. Report first; public renames need the owner's approval.

Idioma del texto original: inglés

audit-analyzer

Audit the EasyEcs analyzer (EECS rules) and code fixes - overlaps, missing rules, false positives, shared detection logic. Use when reviewing or adding analyzer rules or code fixes.

Idioma del texto original: inglés

audit

Run an audit round of EasyEcs (core, generators, analyzer, docs) with parallel agents in worktrees, then triage, merge and verify. Use when asked to review the codebase for redundancy, design problems, missing analyzers or doc gaps, or to "do another round".

Idioma del texto original: inglés

verify

The full EasyEcs gate before merging to master - build, tests, doc fences, API reference, docs site, samples, templates, live demo. Use before any merge or push to master, and after merging audit branches.

Idioma del texto original: inglés