iterative-runner
自動化 Claude 重試循環直到任務完成
複雜任務通常需要多次迭代才能成功。此技能在持續循環中運行 Claude,不斷重試直到測試通過或滿足完成標準。它包含安全限制以防止無限循環,並支援 TDD 工作流程、夜間構建和自動重試邏輯。
스킬 ZIP 다운로드
Claude에서 업로드
설정 → 기능 → 스킬 → 스킬 업로드로 이동
토글을 켜고 사용 시작
테스트해 보기
"iterative-runner" 사용 중입니다. Implement a sorting algorithm using TDD. Write tests first. Output <promise>DONE</promise> when all tests pass. --max-iterations 20
예상 결과:
- Iteration 1: Wrote failing test for empty array case
- Iteration 2: Implemented basic sort, tests still failing
- Iteration 3: Fixed edge case handling, 2 tests passing
- Iteration 4: Optimized performance, all tests passing
- <promise>DONE</promise> - All tests green, implementation complete
"iterative-runner" 사용 중입니다. Build the authentication module. Requirements: login, logout, session management. After 10 failed attempts, list blockers. Output <promise>COMPLETE</promise> when done. --max-iterations 50
예상 결과:
- Attempt 1-3: Researching auth patterns and setting up project structure
- Attempt 4-6: Implementing login flow with validation
- Attempt 7-8: Adding session management and logout functionality
- Attempt 9: Fixing edge cases and adding error handling
- <promise>COMPLETE</promise> - Authentication module built successfully
보안 감사
안전This is a pure documentation-only skill containing no executable code. The SKILL.md file is markdown documentation describing a workflow concept with example shell syntax for illustration purposes only. The skill-report.json is a metadata/configuration file. All static findings are false positives caused by the analyzer misinterpreting documentation examples and metadata as executable code. No network calls, filesystem modifications, or actual command execution are present in this skill.
위험 요인
🌐 네트워크 접근 (1)
📁 파일 시스템 액세스 (1)
품질 점수
만들 수 있는 것
測試驅動開發
通過編寫測試、實現功能並運行測試直到全部通過的持續循環來迭代代碼。
夜間構建自動化
運行需要多次嘗試的複雜構建或部署,無需人工干預直到成功。
不穩定測試恢復
為需要重複嘗試以處理邊緣情況或競態條件的實現自動化重試邏輯。
이 프롬프트를 사용해 보세요
Implement [FEATURE]. Success criteria: [CRITERIA]. Output <promise>DONE</promise> when complete. --max-iterations [N]
Implement feature using TDD: 1) Write failing test, 2) Implement code, 3) Run tests, 4) Fix if failing, 5) Repeat. Output <promise>DONE</promise> when all tests pass. --max-iterations 50
Build [PROJECT]. Requirements: [LIST]. Success: all builds pass. After 15 failed attempts, document blockers. Output <promise>COMPLETE</promise> when done. --max-iterations 100
Implement [COMPLEX FEATURE] in phases: Phase 1: [GOAL1], Phase 2: [GOAL2], Phase 3: [GOAL3]. Each phase outputs <promise>NEXT</promise>. Final phase outputs <promise>DONE</promise>. --max-iterations 30
모범 사례
- 始終指定 --max-iterations 以防止失控循環
- 在開始前定義清晰、可衡量的完成標準
- 對複雜任務使用增量目標以追蹤進度
- 包含在重複失敗後記錄阻礙因素的退出機制
피하기
- 在未定義完成標準的情況下開始迭代
- 省略安全限制 --max-iterations 旗標
- 使用模糊的成功標準,如「讓它運作」
- 在擴展的夜間構建中運行而不監控