本文へ移動
cccskills
無料GitHub で公開

install-loop

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.

インストール方法を見る

含まれるファイル(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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

An advanced skill for L3 autonomous loops. When the token budget nears exhaustion, the agent analyzes its ROI and autonomously drafts a negotiation request for a budget increase rather than silently failing.

日本語の概要は準備中です。原文の説明を表示しています。

cobusgreyling/loop-engineering1.1万2026年10月10日 更新

Scan recent merges and commits since last release for changelog content.

日本語の概要は準備中です。原文の説明を表示しています。

cobusgreyling/loop-engineering1.1万2026年10月10日 更新

Scan recent merges to main (and noteworthy direct commits) since a given window (last tag or date in state). Extract titles, labels, types, linked issues, and signals for breaking changes or security. Produces structured input for a release notes drafter. Use in changelog-drafter loops.

日本語の概要は準備中です。原文の説明を表示しています。

cobusgreyling/loop-engineering1.1万2026年10月10日 更新

Scan merged PRs and commits since a given reference, extract titles, labels, types, and signals. Produces structured input for release notes drafting.

日本語の概要は準備中です。原文の説明を表示しています。

cobusgreyling/loop-engineering1.1万2026年10月10日 更新

Scan recent merges/PRs/commits for release note content. Structured output for drafter.

日本語の概要は準備中です。原文の説明を表示しています。

cobusgreyling/loop-engineering1.1万2026年10月10日 更新

ci-triage

無料

Parse CI failures, identify failing job/step, classify as flake, regression, env, or config. Use in CI sweeper loops before any fix attempt.

日本語の概要は準備中です。原文の説明を表示しています。

cobusgreyling/loop-engineering1.1万2026年10月10日 更新

cobusgreyling のスキルをすべて見る

このスキルの問題を報告する