Install
$ agentstack add skill-byerlikaya-claude-starter-kit-iterate ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Iterate — refine to Done, don't stop at the first attempt
When
A task has an objective acceptance criterion (tests, a review gate, a spec) and the first attempt may not meet it. This is a single-session refinement loop — NOT the harness /loop, which schedules a prompt on an interval. Open-ended exploration with no checkable target does not belong here.
The loop
- Name the exit test first — the concrete, checkable condition that means "done": tests green,
review-agent-csk clean, the spec's acceptance criterion met, zero SonarQube findings. No exit test → go to spec-planning first; a loop without a target never terminates. Prefer an external, machine-grounded verifier — a test exit code, a schema match, a lint/quality gate — over an LLM's self-assessment. A model grading its own output inflates; an "it looks done" or even a single "review clean" with no objective check is a weak verifier. When the only available check is a judgment call, ground it (a second agent with a distinct lens, an explicit rubric) rather than trusting the loop's own say-so.
- Run one round: change → verify (drive the real flow, not only tests) → check the exit test.
- Report the gap every round — state what still fails and why. Never loop silently.
- Repeat until the exit test passes. Stop early and surface it if: two rounds pass with no new
progress (you are stuck — report, don't spin), the exit test itself is wrong, or a blocker needs a decision from the user.
- Close at the DoD gate, not at a commit.
commit-agent-cskstill proposes and waits for §4.4
approval. The loop never commits, pushes, or deploys on its own.
Guardrails
- Bounded, not infinite. A fixed exit test plus a no-progress stop is the whole point; "keep trying
forever" is a bug, not diligence.
- Token discipline ([[token-budget]]): each round re-pays for context. Keep a round's output a summary,
push heavy logs to docs/*.md, and don't fan out a subagent per round unless isolation demands it.
- Don't move the goalposts. Never weaken the exit test to end the loop — fix the work, or stop and ask.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: byerlikaya
- Source: byerlikaya/claude-starter-kit
- License: MIT
- Homepage: https://www.npmjs.com/package/@byerlikaya/claude-starter-kit
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.