본문으로 건너뛰기
cccskills
무료GitHub에 공개

install-loop

Set up Loop Engineering through a single command-line tool, choosing a workflow pattern and agent tool. Start in report-only mode, check setup health and readiness, and provide next actions and first-run instructions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Install Loop Engineering into a project via the unified CLI front door (@cobusgreyling/loop). Prefer this over invoking loop-init / loop-audit separately. Week-one is report-only; never enable auto-merge or unattended fixes unless the human explicitly asks and doctor is healthy.

설치 방법 보기

이럴 때 유용합니다

  • Introducing a daily issue and priority review workflow
  • Setting up workflows for stalled pull requests or failing CI
  • Checking the health of an existing Loop Engineering setup
  • Estimating costs before scheduling frequent runs

포함된 파일(1)

  • SKILL.md2.5 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Install Loop Engineering

Goal

Leave the repo with a scaffolded report-only loop, a Loop Ready score, and clear next actions — using the single CLI:

npx @cobusgreyling/loop

Do not deprecate or remove existing loop-init / loop-audit usages you find; both doors stay valid. Prefer loop for new work.

Steps

  1. Detect context

    • If LOOP.md or STATE.md already exists, run doctor only (skip init unless human asks to re-scaffold):
      npx @cobusgreyling/loop doctor . --json
      npx @cobusgreyling/loop status .
      
    • Otherwise continue.
  2. Pick pattern (default: daily-triage)

    PainPattern
    Morning chaos / unclear prioritiesdaily-triage
    PRs stallingpr-babysitter
    CI red / flakesci-sweeper
    CVE / Dependabot noisedependency-sweeper
    Post-merge TODOspost-merge-cleanup
    Stale release noteschangelog-drafter
    Noisy issuesissue-triage
    One GitHub Action, almost no filesthin-loop
  3. Pick tool — claude | grok | codex | opencode (default claude).

  4. Scaffold

    npx @cobusgreyling/loop init . --pattern <pattern> --tool <tool>
    

    Optional harness (only if human wants Foundry): add --with-foundry.

  5. Doctor

    npx @cobusgreyling/loop doctor .
    
    • Exit 0 = healthy · 1 = warnings · 2 = blocked
    • Follow the top 3 printed actions; do not invent extra architecture.
  6. Cost check before high-cadence schedules:

    npx @cobusgreyling/loop cost -p <pattern> -l L1 -c 1d
    
  7. Week-one rule

    • Report only. No auto-fix, no auto-merge.
    • Tell the human the first /loop or scheduler command from init output.
    • Suggest badge only when score is strong: npx @cobusgreyling/loop badge .

Compatibility

These remain fully supported (do not rewrite existing docs/scripts unless asked):

npx @cobusgreyling/loop-init .
npx @cobusgreyling/loop-audit . --suggest

Stop conditions

  • Stop after doctor + first-run instructions unless the human asks for L2+.
  • Never expand into fleet/memory/foundry unless score ≥ 80 and human opts in.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Drafts a token budget extension request when an autonomous loop approaches its daily limit and high priority work remains. Uses logged results and remaining issues to justify the request, then pauses until a human increases the budget.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Requesting extra budget for remaining critical work
  • Summarizing daily token spending and successful actions
  • Preparing a budget request for a human maintainer
cobusgreyling/loop-engineering1.2만2026년 10월 18일 업데이트

Scans merged pull requests and commits since a chosen reference, using titles, labels, milestones, and messages to categorize changes. Produces a release notes draft, highlights breaking changes and security items, and records the scan window.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Collecting changes since the previous release tag
  • Sorting updates into features, fixes, and other categories
  • Identifying breaking changes and security items
cobusgreyling/loop-engineering1.2만2026년 10월 18일 업데이트

Scan recent merges, pull requests, and commits for release note material. Produce structured entries and a summary with PR references, highlighting breaking changes and security items while filtering routine dependency and bot noise.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Gathering release note material from recent changes
  • Identifying breaking changes and security items
  • Organizing changes with PR references
cobusgreyling/loop-engineering1.2만2026년 10월 18일 업데이트

Scan merges and commits since the previous release to collect user-facing changes for a changelog. Produce structured entries and a summary, with explicit lists of breaking changes and security signals.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Collecting changes since the previous release
  • Organizing user-facing updates
  • Listing breaking changes and security signals
cobusgreyling/loop-engineering1.2만2026년 10월 18일 업데이트

Review merged pull requests and significant commits within a release window, then organize features, fixes, breaking changes, and security signals into structured source material for drafting release notes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Collecting changes since the last release
  • Checking breaking changes and security signals
  • Preparing source material for release notes
cobusgreyling/loop-engineering1.2만2026년 10월 18일 업데이트

ci-triage

무료

Analyze failures in CI, the automated checks run during development. Identify the failing job and step, classify the likely cause, and suggest a small fix, continued monitoring, or human review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Identifying failed jobs and steps in CI
  • Distinguishing intermittent failures from code regressions
  • Routing environment failures to a human
cobusgreyling/loop-engineering1.2만2026년 10월 18일 업데이트

cobusgreyling의 스킬 모두 보기

이 스킬의 문제 신고