trellis-auto-loop

Drives unattended batch task execution through the Trellis auto_loop.py runner.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/SilentFlower/flower-trellis --skill trellis-auto-loop-silentflower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-auto-loop
Source: https://github.com/SilentFlower/flower-trellis/tree/main/.agents/skills/trellis-auto-loop
Command: npx skills add https://github.com/SilentFlower/flower-trellis --skill trellis-auto-loop-silentflower

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Running multiple Trellis tasks one by one requires constant manual confirmation, route selection, and status tracking. This Skill automates the full loop: preparing tasks, resolving open questions, implementing, checking, and committing locally, all driven by the authoritative auto_loop.py runner state. ## Core Features & Use Cases - Unattended Batch Runs: Start a commit-only run over an explicit task list with dependency declarations, check depth, and implement/check route modes. - Runner-Driven Actions: Execute prepare and running actions (classify dirty baselines, resolve open questions, run implement/check/fix, commit-only) and record each result precisely before advancing with next. - Bounded Autonomous Decisions: Log low-risk local decisions via the decide command with evidence and risk levels, while blocking irreversible or scope-expanding changes. - Recovery Protocols: Handle retryable artifact-drift and recovery diagnostics with a three-attempt correction budget using the reconcile flow in references/artifact-recovery.md. - Use Case: A developer with five planned Trellis tasks starts an auto-loop run; the Skill prepares all tasks, resolves open questions with the user once, then implements, checks, and locally commits each task without further prompts, ending with a pending-archive handoff report. ## Quick Start Ask the AI to start a Trellis auto-loop run over your listed tasks and let it drive auto_loop.py through prepare, implement, check, and local commit until the queue finishes.

Frequently Asked Questions about trellis-auto-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run multiple Trellis tasks automatically?▼

Start an auto-loop run with auto_loop.py start, passing an explicit task list, the commit-only profile, and optional dependency, check-depth, and route flags. The runner then issues actions that the agent executes and records until the queue reaches a terminal state.

How do I resume a Trellis auto-loop run after interruption?▼

Run auto_loop.py resume followed by auto_loop.py next to continue the outstanding action. The runner replays the original action with its baseline, and schema 1 runtimes keep their original action flow.

Can the auto loop push, merge, or deploy commits?▼

No. Local commit is the automatic endpoint; push, merge, release, deploy, finish-work, and archive are forbidden inside the loop. Completed tasks are marked locally completed and archiving always requires explicit user action.

What happens when a record returns retryable artifact-drift?▼

Do not run next; keep the outstanding action and correct within it. Revert mistaken edits or declare exact doc-remediation files, then re-record, with at most three retryable corrections before the action becomes terminally blocked.

When can the AI make decisions on its own in auto loop?▼

Only for choices within the task goal that affect local code, are reversible and verifiable, and carry low or medium risk. These must be logged via the decide command with evidence; irreversible, security-reducing, or scope-changing matters must be blocked.