agentleFS
blas1nblas1n/claude-skills/skills/completion-detector-fires-on-an-earlier-success-string/SKILL.md

completion-detector-fires-on-an-earlier-success-string

Skill2 starsChanged 57 days agoNo licenceView on GitHub

긴 작업을 기다리는 폴링 루프의 패턴이 **종료 이벤트에만** 나타나는 문자열이 아니면, 앞선 단계의 성공 메시지에 걸려 일찍 끝난다 — "끝났다"는 알림이 오는데 결과는 아직 없다. 체인된 게이트(`ruff && mypy && pytest`)에서 특히 잘 터진다. 종료 신호는 **형태로 유일**해야 하고, 안 되면 마커를 직접 심어라. 트리거 - `until grep -q ...` 대기, `tail -f | grep` 완료 감지, CI/배포 폴링, 여러 도구를 && 로 묶은 게이트.

The file

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.