self-improve

You can audit a codebase for behavior-preserving improvements by invoking the self-improve workflow, which identifies obvious professional polish, applies changes, and orchestrates two-pass verification to ensure observable behavior remains intact.

Polishing code without redesigns requires applying obvious, behavior-preserving improvements aligned to craft, test, and autonomy rules, enabling continuous iteration while maintaining the existing observable behavior of the software.

Yes, you can run an audit on a single feature or module. The auditing workflow is scope-flexible, allowing you to target an entire project, a specific screen, a feature, or an individual module for improvements.

Two-pass verification works by enforcing kit rules during the codebase audit, automatically generating per-improvement tasks, and validating that applied changes preserve observable behavior before outputting a draft pull request.

Yes, the workflow enforces validation through specific kit rules including craft-rules.md, test-rules.md, and autonomy-rules.md to verify behavior-preserving changes before generating tasks and a draft pull request.