ck:loop

Automate iterative optimization of a measurable software metric via git-tracked experiments.

Updated May 10, 2026
One-click install
npx skills add https://github.com/dthuy62/kollet-app --skill ck-loop-dthuy62
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:loop
Source: https://github.com/dthuy62/kollet-app/tree/main/.opencode/skills/ck-loop
Command: npx skills add https://github.com/dthuy62/kollet-app --skill ck-loop-dthuy62

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates repeated code changes toward a measurable target, so you can improve metrics like coverage, bundle size, lint errors, or performance without manually managing each experiment.

Core Features & Use Cases

  • Metric-driven iteration: Runs a defined optimization loop across multiple rounds and compares each result against the previous best.
  • Git-safe experimentation: Commits before verification, preserves history, and reverts discarded changes to keep experiments traceable.
  • Guarded optimization: Supports a separate regression check so improvements are only kept when the broader project still passes validation.
  • Use case: Ideal for engineering tasks such as raising test coverage in a code area, reducing bundle size, or eliminating repeated build and lint issues.

Quick Start

Ask the skill to improve one measurable metric in a defined scope and include the verify command, optional guard command, and iteration limit.

Frequently Asked Questions about ck:loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate iterative test coverage improvement across a specific file scope?

Automated test coverage improvement runs repeated git-tracked experiments across a defined file scope, committing changes before verification and reverting discarded ones to preserve history while incrementally raising coverage metrics.

What is metric-driven code optimization and how does git-tracked iteration work?

Metric-driven code optimization applies repeated git-tracked experiments toward a measurable target like bundle size or lint errors, comparing each result against the previous best to decide whether changes are kept or discarded.

Can I guard against regression while optimizing bundle size or lint cleanup?

Yes, bundle size reduction and lint cleanup support a separate regression guard command, ensuring improvements are only kept when the broader project still passes validation alongside the primary metric verification.

What do I need to set up before running automated iteration on a measurable software metric?

You need a defined file scope, a single numeric verify command to measure the target metric, an optional regression guard command, and explicit iteration and delta settings to determine when changes are kept or discarded.

What's the best way to automate performance tuning without losing git history?

Automated performance tuning commits before each verification run and reverts discarded changes, keeping experiments fully traceable in git history while iteratively improving the measurable performance metric.

Why does my metric optimization loop discard changes that improved the target number?

Changes are discarded when the numeric verify command shows improvement but the optional regression guard fails, or when the delta between iterations falls below the explicit threshold defined in the iteration settings.