One-click install
npx skills add https://github.com/jangtrinh/demo-Lam --skill ck-loop-jangtrinh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:loop
Source: https://github.com/jangtrinh/demo-Lam/tree/main/.claude/skills/ck-loop
Command: npx skills add https://github.com/jangtrinh/demo-Lam --skill ck-loop-jangtrinh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

ck:loop helps you improve a measurable metric through repeated, controlled experiments with automatic commit/rollback so you can move toward better results without manually tracking every try.

Core Features & Use Cases

  • Autonomous iterative optimization: Runs up to N iterations, generating one focused change per iteration, verifying improvement, and deciding keep vs discard.
  • Git-history based safety: Commits before verification and uses reverts to roll back regressions while preserving experiment history for pattern learning.
  • Guarded quality regression checks: Supports a separate Guard command to ensure the optimization doesn’t break unrelated correctness (if Guard fails, it reverts and reworks).
  • Results logging for trend analysis: Appends iteration outcomes to loop-results.tsv to track progress, delta, keep/discard status, and explanations.

Quick Start

Run ck:loop with a Goal, a file Scope glob, and a Verify command that prints exactly one numeric value so it can iteratively improve that metric.

Frequently Asked Questions about ck:loop

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

FAQPage Schema
How do I autonomously optimize code metrics like test coverage or bundle size?

Autonomous iterative optimization works by applying one atomic change per iteration, using a Verify command that outputs a single number to decide whether to keep or discard the modification. It commits before verification and reverts regressions while preserving experiment history for pattern learning.

Can I automatically revert code changes that cause performance regressions?

Automatically reverting regressions is handled by guard-and-revert logic that commits before verification and rolls back any changes failing the Guard check. This ensures unrelated correctness is preserved while moving toward better measurable results.

What is metric-driven verification for iterative code search?

Metric-driven verification requires a Verify command that prints exactly one numeric value to confirm whether an atomic change improved the target metric. Iteration outcomes, including deltas and keep/discard status, are appended to a TSV file for trend analysis.

Do I need a clean git working tree for autonomous optimization loops?

A clean git working tree is a strict precondition enforced before starting autonomous optimization loops. This ensures the system can safely commit experiments, track iteration deltas, and revert regressions without conflicting with uncommitted local changes.

How do I track progress and deltas during autonomous performance tuning?

Tracking progress during autonomous performance tuning is handled by appending iteration outcomes to a loop-results.tsv file. This log records the delta, keep or discard status, and explanations for each attempt, enabling trend analysis and pattern learning from the experiment history.