Verified:GitHub

loop-setup

Detect GitHub, GitLab, or local trackers and generate a unified .loop/config.md.

5|Updated Mar 30, 2026

Search Tags:#automation #workflow #github #gitlab #loop-setup #tracker-detection #config.md

One-click install

npx skills add https://github.com/kenlck/skills --skill loop-setup

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: loop-setup
Source: https://github.com/kenlck/skills/tree/main/ken-loop/skills/loop-setup
Command: npx skills add https://github.com/kenlck/skills --skill loop-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Loop Setup enables immediate, tracker-agnostic initialization for loop-engineering by auto-detecting the issue tracker and generating a standardized .loop/config.md that defines five core verbs for loop-issues and work-issues.

Core Features & Use Cases

Detects the active tracker (GitHub/GitLab/local) and asks for confirmation before applying changes.
Creates or validates backend-specific artifacts, such as GitHub/GitLab labels or local workspace scaffolding.
Writes a canonical .loop/config.md detailing five verbs (next-ready, read, comment, set-status, link-pr) with concrete commands.
Verifies configuration by exercising read-only verbs to ensure the setup works in the repository.

Quick Start

Run this skill in your repository to generate the .loop/config.md after confirming the tracker choice.

Frequently Asked Questions about loop-setup

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

FAQPage Schema

How do I initialize loop-engineering in an existing repository?▼

To initialize loop-engineering, run the setup skill in your repo to auto-detect the issue tracker and generate a unified .loop/config.md. This file defines five core verbs for loop-issues and work-issues.

How does tracker detection work for GitHub and GitLab projects?▼

Tracker detection works by scanning your repository to identify GitHub, GitLab, or local environments, then asking for confirmation before applying backend-specific artifacts like labels or local workspace scaffolding.

What is a .loop/config.md file and what does it contain?▼

A .loop/config.md file is a canonical configuration documenting five core verbs: next-ready, read, comment, set-status, and link-pr. It provides concrete commands for managing loop-issues and work-issues.

Can I use loop-engineering workflows with a local issue tracker instead of GitHub or GitLab?▼

Yes, you can use local issue tracking. The setup detects local environments and creates or validates local workspace scaffolding, ensuring a tracker-agnostic, ready-to-run loop process.

How do I verify my loop-engineering configuration is set up correctly?▼

Verify the configuration by exercising read-only verbs like next-ready and read commands. This tests the setup to ensure the tracker integration works properly in your repository.

Does loop-engineering setup modify existing GitHub or GitLab repository labels?▼

The setup creates or validates backend-specific artifacts like GitHub or GitLab labels. It detects the active tracker and asks for confirmation before applying changes to your repository.