dev-loop

Process open issues sequentially by dispatching a sub-agent per item.

118|12|Updated May 5, 2026

Search Tags:#automation #issue-tracking #git-workflow #dev-loop #autonomous-agent #code-maintenance

Ready to run

npx skills add https://github.com/alecs5am/ralphy --skill dev-loop-alecs5am

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-loop
Source: https://github.com/alecs5am/ralphy/tree/main/.agents/skills/dev-loop
Command: npx skills add https://github.com/alecs5am/ralphy --skill dev-loop-alecs5am

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the maintainer's workflow by orchestrating an autonomous, issue-driven development loop over Ralphy's own notes/issues, reducing manual coordination and speeding fixes.

Core Features & Use Cases

Dispatch a single sub-agent per issue with a scoped mandate and deterministic execution order.
Sort and execute issues by dependency, ensuring sequential processing to avoid conflicts.
Commit changes after each issue and move them to notes/issues/done/ with a timestamp for traceability.
Provide a structured report and guardrails for paid-generation and irreversible actions.

Quick Start

Invoke the dev-loop to begin processing open issues in notes/issues/ with the default 25-issue limit, and observe sequential, committed updates.

Frequently Asked Questions about dev-loop

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

FAQPage Schema

How do I automate processing open issues in a git workflow?▼

Automate issue processing by dispatching a sub-agent for each item sequentially, sorting by dependency, committing changes, and moving completed files to a done folder for traceability.

How does an autonomous dev loop handle issue dependencies?▼

An autonomous dev loop handles dependencies by building a deterministic execution order, processing issues sequentially to avoid conflicts, and dispatching scoped agents per issue.

Can I use an autonomous agent for code maintenance without irreversible actions?▼

Yes, the autonomous agent enforces guardrails against irreversible actions and paid-generation gates, committing changes only after each scoped evaluation completes successfully.

What is the best way to track completed git-workflow issues automatically?▼

Track completed issues automatically by moving resolved items into a dedicated notes/issues/done folder with a timestamp, providing a structured report of all execution outcomes.

Are there limits to sequential issue-driven development automation?▼

Sequential issue-driven development automation defaults to a 25-issue processing limit per invocation, ensuring deterministic execution order and scoped sub-agent mandates without concurrent conflicts.

Does the dev-loop automation work without external dependencies?▼

Yes, the dev-loop automation operates without external dependencies, relying solely on local notes/issues directories to orchestrate scoped sub-agents and commit resolved changes.