Devloop

[English](./README.md) | [简体中文](./README.zh-CN.md)

devloop

**A controlled PR/MR development lifecycle for AI coding agents.**

This repository is a cross-CLI plugin marketplace. Its flagship plugin, `devloop`, helps Claude Code and Codex complete branch-based development without losing control of repository state, validation, Git mutations, or concurrent sessions.

The marketplace also distributes `code-taste`, a skill-only plugin for architecture, boundaries, naming, maintainability, documentation, and code review, plus `quality`, a skill-only plugin for evidence-driven project quality evaluation.

enter repo → start branch → develop → normalize → lint ∥ test → commit → push → PR/MR → human merge

devloop supports GitHub PRs and GitLab MRs, selected from each repository's origin. Merge remains a human decision.

Why devloop

AI coding often loses time at the boundaries around the code:

• Information lag — the agent guesses the current repository, branch, PR/MR, and validation state from conversation history.
• Soft conventions do not enforce themselves — instructions such as “do not commit to main” or “do not use git add -A” can still be bypassed without execution-level guards.
• Concurrent sessions collide — multiple agents sharing one checkout can switch branches underneath each other, mix uncommitted work, or resolve an operation to the wrong repository.

devloop turns those boundaries into a reusable development loop: live context tells the agent where it is, controlled transactions own Git side effects, validation runs against affected Components, and managed worktrees isolate concurrent work.

What the devloop plugin provides

• Controlled Git/PR transactions — gcam, gcamp, and gcampr perform commit, commit + push, and commit + push + PR/MR respectively. New work starts from the intended target branch instead of inheriting accidental commits from the current HEAD.
• Affected-Component validation — a repositor