ballroom-flow-change-control

Change control enforces branching from the development branch, discourages direct pushes to main, and requires TDD, linting, and type checking to maintain code quality. It classifies changes into categories like domain logic and web UI with specific associated guidelines.

Aligning code changes with project documentation requires ensuring all modifications comply with the docs/PLAN.md file. This change control process validates that updates to domain logic, web UI, or worker code strictly match the predefined project documentation.

Classifying repository changes involves categorizing modifications into domain logic, web UI, or worker code. Each category triggers specific change management guidelines, ensuring thorough testing, documentation alignment, and proper code review processes before merging.

No, this change control skill explicitly discourages direct pushes to the main branch. It enforces a branching strategy where all changes must branch from the development branch to ensure proper review, testing, and documentation compliance.

Yes, test-driven development is required to manage changes in the Weave Steps repository. The change control guidelines mandate implementing TDD alongside linting and type checking to enforce code quality standards before any code review.

Repository updates fail change management checks when changes lack proper testing, bypass the development branch, or do not align with docs/PLAN.md. Enforcing these coding practices ensures collaboration and code quality standards are met before integration.