Feat loop action

[THRISHAL12345]

Summary

Introduces the loop-action GitHub Composite Action to seamlessly integrate the Loop Engineering safety suite (readiness audit, circuit breaker, and worktree sandboxing) into CI workflows, while refactoring all example workflows to significantly reduce boilerplate.

Changes

• New pattern or starter (followed templates/pattern-template.md and updated registry.yaml)
• Documentation / example improvement
• Tool changes (loop-action)
• Story (includes a real failure or surprise and the lesson learned)

Checklist (from CONTRIBUTING)

• All required sections are present for patterns
• Links work from README.md, patterns/README.md, starters/README.md, and docs/index.md
• No secrets, tokens, or internal company URLs
• STATE.md examples use the .example suffix
• Safety-related content references docs/safety.md
• Ran node tools/loop-audit/dist/cli.js . (or on the starter) and addressed all findings

Testing / Dogfooding

• loop-audit passes on the affected starters or this repository
• Manually reviewed the generated state and skill output

Screenshots / Examples

Boilerplate Reduction in dependency-sweeper.yml

Before (manual setup)

- name: Circuit breaker check
  id: circuit_breaker
  run: |
    npx --yes @cobusgreyling/loop-context --check --ledger loop-ledger.json \
      --budget-from-pattern dependency-sweeper --budget-level L2 || echo "tripped=true" >> "$GITHUB_OUTPUT"
  continue-on-error: true

- name: Placeholder — wire to your agent runtime
  if: steps.circuit_breaker.outputs.tripped != 'true'
  run: |
    echo "Run dependency-triage (npm audit / outdated)."

---

After (using loop-action)

- name: Invoke Dependency Sweeper Agent
  uses: cobusgreyling/loop-engineering/tools/loop-action@main
  with:
    pattern: "dependency-sweeper"
    level: "L2"
    sandbox: "true"
    sandbox-shell: "true"
    command: |
      echo "Run dependency-triage (npm audit / outdated)."

[github-actions]

Thanks @THRISHAL12345 for contributing a tool example — visible, reviewable PRs like this grow the reference for everyone.

What happens next

• Maintainer aims for same-day review on story, adopter, and scoped docs/example PRs (CONTRIBUTING.md).
• good first issue PRs: comment on the linked issue so we can assign and close on merge.

More ways to help

• Contributor quickstart + open issues
• Good first issue backlog

— loop-engineering maintainers