ck:autoresearch

Automate test coverage improvement by running an autonomous optimization loop that applies one atomic change at a time, measures the numeric result, and commits verified progress. It uses git commits and reverts as a built-in rollback system for safe iteration.

Reduce bundle size safely by running an autonomous iterative optimization loop with a guarded verification check. This ensures metric improvements are measured against a numeric target and a separate regression guard prevents breaking the rest of the project.

Yes, autonomous optimization applies to repository-scoped tasks like lint cleanup and performance tuning. It requires a numeric verification command to measure success and an optional regression guard to ensure changes do not break existing project functionality.

Rollback-safe iteration uses git commits and reverts as a built-in history system. The optimization loop plans a change, measures the result, and decides whether to keep the commit or revert it, ensuring only verified progress is saved.

Yes, a numeric verification command is required to start automating code metric improvements. The optimization loop relies on this measurable target to evaluate each atomic change, alongside an optional regression guard and git-tracked file scope.

The optimization loop is limited to repository-scoped tasks with clear numeric success metrics. It requires a measurable verification command and git-tracked commits, meaning tasks without quantifiable targets or non-repository file scopes are not suitable.