Stephenson-Software

Create Dev Loop — Git skill for Claude Code

Git community

Claude Code skill that generates a tailored autonomous dev loop for any git repository.

How to install Create Dev Loop

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Stephenson-Software/create-dev-loop and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Create Dev Loop does

Claude Code skill that generates a tailored autonomous dev loop for any git repository.

Alternatives in Git

Fullstack Dev Skills — by jeffallan - A comprehensive Claude Code plugin with 65 specialized skills covering full-stack development a 7k ★
Perfup — Autonomous performance optimization: research, PoC, benchmark, implement, review, PR 3.6k ★
Win Dev Skills — Agent plugins for building Windows apps with GitHub Copilot, Claude Code, OpenAI Codex, and more 463 ★

README

create-dev-loop

[![CI](https://github.com/Stephenson-Software/create-dev-loop/actions/workflows/ci.yml/badge.svg)](https://github.com/Stephenson-Software/create-dev-loop/actions/workflows/ci.yml) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE.md)

A Claude Code skill that generates a **tailored autonomous dev loop** for any git repository — one slash command away from continuous, repo-aware development.

Why a tailored dev loop?

Generic AI coding assistants treat every repo the same. A tailored dev loop encodes what makes *your* repo tick:

Generic assistant	Tailored dev loop
Guesses your test command	Knows `./mvnw test` vs `cargo test` vs `pytest`
Ignores your PR template	Fills it in from your PR template, whichever spelling and location it uses
Doesn't know your branch convention	Enforces `feature/` or `fix/` based on your `CONTRIBUTING.md`
Skips your linter	Runs `ruff check` / `eslint` / `golangci-lint` before every push
Opens PRs with placeholder reviewers	Requests the right person from `CODEOWNERS` or adds `Copilot`
Repeats the same mistakes	Self-audits each cycle and files improvement issues

When Claude knows your build system, test suite, doc sources, and reviewer patterns, it doesn't drift. It ships work that passes CI, matches your conventions, and closes the right issues — without hand-holding.

What it does

Running `/create-dev-loop` in any repo runs seven Steps (mapped 1:1 to Steps 1–7 of `create-dev-loop.md`):

Identify the repository — confirms a git toplevel, derives the slug, checks whether a skill already exists and (if so) asks update / overwrite / cancel
Explore — reads CLAUDE.md, CONTRIBUTING.md, CI workflows, build files, linter configs, recent PRs, and CODEOWNERS to compile a repo-specific profile (build/test commands, branch prefix, reviewer, doc sources, code patterns)
Write the skill file at `~/local-skills/<