dev-loop

Automate code change workflows with investigate, fix, test, deploy, and QA steps.

8|1|Updated Aug 5, 2025
One-click install
npx skills add https://github.com/ArtyMcLabin/ClaudeCode-global-config --skill dev-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-loop
Source: https://github.com/ArtyMcLabin/ClaudeCode-global-config/tree/main/skills/dev-loop
Command: npx skills add https://github.com/ArtyMcLabin/ClaudeCode-global-config --skill dev-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates a universal development workflow for all code changes.

Core Features & Use Cases

  • Universal development pipeline: investigate → fix → test → deploy → QA, applied to any code change across repositories.
  • Scope-aware coordination: supports per-workspace overrides and continuous scanning mode for autonomous operation.
  • Governance and cadence: enforces mandatory steps (investigate, plan, fix, test, commit, deploy, QA, report) and aligns with deployment policies.

Quick Start

Trigger the dev-loop in your workspace using a command like 'start dev loop' and follow the prompts to investigate, plan, fix, test, deploy, and QA.

Frequently Asked Questions about dev-loop

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

FAQPage Schema
What is a standard development pipeline for code changes?

A universal development pipeline enforces mandatory steps for code changes: investigate, plan, fix, test, commit, deploy, QA, and report. This workflow aligns with deployment policies like auto-prod, auto-stage, or approval-required.

How do I automate the development workflow across multiple repositories?

Automate the development workflow across repositories by triggering a continuous scanning mode. This applies the universal pipeline to any code change, including bug fixes, features, and refactors, while supporting per-workspace overrides.

How do I enforce QA and testing steps before deployment?

Enforce QA and testing steps before deployment by applying a mandatory development pipeline. The pipeline requires investigate, fix, and test phases, followed by QA submission via the per-project QA skill before any deployment proceeds.

Can I apply per-workspace overrides to my deployment policy?

Yes, you can apply per-workspace overrides to your deployment policy. The development pipeline supports scope-aware coordination, allowing specific workspaces to align with auto-prod, auto-stage, or approval-required policies.

Does this development pipeline support continuous scanning mode for autonomous operation?

Yes, the development pipeline supports continuous scanning mode for autonomous operation. This scope-aware coordination automatically applies the investigate, fix, test, deploy, and QA steps to code changes across your repositories.

What is the best way to manage deployment policies for bug fixes and features?

Manage deployment policies for bug fixes and features by enforcing a universal development pipeline. This aligns code changes with your governance cadence, routing deployments to auto-prod, auto-stage, or approval-required based on policy.