boucle

Automates issue-to-production feature delivery through a label-driven CI agent pipeline.

2|Updated Jul 25, 2026
One-click install
npx skills add https://github.com/ankaboot-source/boucle --skill boucle-ankaboot-source
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: boucle
Source: https://github.com/ankaboot-source/boucle
Command: npx skills add https://github.com/ankaboot-source/boucle --skill boucle-ankaboot-source

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a forge issue into a reviewed, merged, and deployed feature normally requires manual coordination across coding, review, merge, and verification steps. This Skill encodes the boucle protocol so an agent can drive that entire loop autonomously on GitLab or GitHub CI, with the human intervening only at spec-approval and MR-approval gates. ## Core Features & Use Cases - Label-driven state machine: Issues move through triage, worker, reviewer, merge, deploy, and e2e stages via boucle: labels, with SHA-anchored verdicts and marker-stamped comments preventing self-trigger loops. - Forge-agnostic operation: A forge abstraction layer (bin/forge/gitlab.sh, bin/forge/github.sh) lets the same loop run on GitLab CI or GitHub Actions, including mono-user mode without a separate bot account. - Self-healing and self-improvement: A scheduled doctor sweep recovers stuck issues, and a LESSONS.yml admission workflow captures reusable lessons from failed iterations. - Use Case: A product builder opens an issue describing a UI change, adds the boucle:triage label, and the loop triages it, implements on a worker branch, deploys a preview, runs adversarial review, merges after a thumbs-up, and verifies production with a SHA-anchored e2e gate. ## Quick Start Add the boucle:triage label to a forge issue and assign it to the bot so the loop triages, implements, reviews, merges, deploys, and verifies the feature end to end.

Frequently Asked Questions about boucle

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

FAQPage Schema
How do I trigger the boucle loop on an issue?

Add the boucle:triage label to the issue and assign it to the bot account. The dispatch webhook routes it to the triage role, which posts a structured spec; approving with a thumbs-up starts the worker.

Does boucle work with GitHub Actions or only GitLab CI?

Boucle supports both forges through a forge abstraction layer in bin/forge/. GitLab is the reference implementation using glab; GitHub works via gh but scheduled doctor sweeps are throttled by the platform, so recovery relies more on webhook-driven opportunistic sweeps.

Can I run boucle without a separate bot account?

Yes, mono-user mode (bin/setup --mono-user) lets one account own both issues and the loop. Anti-loop protection then relies solely on the invisible boucle:agent comment marker instead of actor-identity checks.

What happens when the worker agent fails or produces no changes?

CI detects empty MRs by comparing base and head SHAs and re-triggers the worker or escalates to a human. A doctor sweep also re-triggers stuck issues past the staleness threshold, and iteration caps prevent infinite retries.

How does boucle prevent review of broken code?

The reviewer tests against a deployed preview URL rather than reading diffs, and the e2e stage verifies production with a SHA-anchored verdict comment. A failed verdict at either gate routes the issue back to the worker.