By zate
Lightweight development workflow with plan/run/fresh pattern, git workflow integration, PR feedback, and autonomous execution. Optimized for efficiency - minimal hooks, on-demand skills, direct execution.
npx claudepluginhub zate/cc-plugins --plugin devloopUse this agent to generate or update READMEs, API docs, inline comments, and changelogs. Use when: User asks to write or update documentation, README, API docs, CHANGELOG, or code comments. Do NOT use when: User needs code exploration (use engineer), test writing (use qa-engineer), or security analysis (use security-scanner). <example> user: "Update the API documentation" assistant: "I'll launch devloop:doc-generator to document the API changes." </example>
Use this agent for code exploration, architecture design, refactoring analysis, git operations, and code review. Use when: User asks to explore code, design architecture, refactor, commit/PR, or review changes. Do NOT use when: User needs test generation (use qa-engineer), security audit (use security-scanner), or documentation (use doc-generator). <example> user: "How does the payment processing work?" assistant: "I'll launch devloop:engineer to explore the payment system." </example> <example> user: "Create a PR for this feature" assistant: "I'll use devloop:engineer to handle the git workflow." </example> <example> user: "Review my changes before commit" assistant: "I'll launch devloop:engineer in reviewer mode to review your code." </example>
Lightweight autonomous task executor for simple/mechanical plan tasks. Uses haiku model for cost efficiency. Use when: Orchestrator needs a cheap worker for tests, docs, formatting, linting, config changes, or file renames. Do NOT use when: Task requires complex reasoning, multi-file architecture, debugging, or security analysis. <example> Context: The orchestrator is running devloop:run and encounters a [model:haiku] task assistant: "I'll spawn a haiku-worker for this simple task." </example>
Use this agent for test generation, test execution, bug tracking, and deployment validation. Use when: User asks to write tests, run tests, track bugs, or validate deployment readiness. Do NOT use when: User needs code review (use engineer), security scan (use security-scanner), or code exploration (use engineer). <example> user: "Write tests for the new UserService" assistant: "I'll launch devloop:qa-engineer to create tests." </example> <example> user: "Run the tests" assistant: "I'll use devloop:qa-engineer to run tests and analyze results." </example>
Use this agent for security vulnerability scanning including OWASP Top 10, hardcoded secrets, and injection risks. Use when: User asks about security, vulnerabilities, hardcoded secrets, injection risks, or OWASP compliance. Do NOT use when: User needs code review for quality (use engineer), test generation (use qa-engineer), or general code exploration (use engineer). <example> user: "Check if this auth code is secure" assistant: "I'll launch devloop:security-scanner to analyze security." </example>
Autonomous task executor for devloop:run-swarm. Implements a single plan task with fresh context. Do not use for interactive work. Use when: Orchestrator is running swarm mode and needs to parallelize independent plan tasks. Do NOT use when: Interactive work is needed, or for single-task execution (just do the work directly). <example> Context: The orchestrator is running devloop:run-swarm and needs to execute a plan task assistant: "I'll spawn a swarm-worker to implement this task with fresh context." </example>
This skill should be used for REST API, GraphQL, versioning, pagination, authentication, backend routes, web services, HTTP endpoints, server API design
This skill should be used for system design, design patterns, architectural decisions, SOLID principles, clean code structure, code organization, refactoring strategy, software architecture
Archive a completed plan to .devloop/archive/
This skill should be used for guidance on commit size, scope, and creating reviewable commits, splitting large changes, commit hygiene
This skill should be used for database schema design, indexes, query optimization, migrations, SQL, PostgreSQL, MySQL, ORM patterns, data modeling, database relationships
Audit devloop against Claude Code updates to identify integration opportunities. Use after Claude Code releases, monthly maintenance, or when exploring new features.
Start development workflow - lightweight entry point
Save current plan state and prepare for fresh context restart
This skill should be used for branching strategies, conventional commits, PR workflows, and release management, git flow, trunk-based development, merge strategies
This skill should be used for Go idioms, error handling, goroutines, interfaces, and testing, golang, Go language, Go modules, Go concurrency
Learn how to use devloop - interactive guide to commands, workflow, and best practices
List GitHub issues for the current repository
This skill should be used for Java/Spring patterns, dependency injection, streams, Optional, Kotlin, Spring Boot, Maven, Gradle, JVM backend
This skill should be used for configuring devloop project settings via .devloop/local.md, git workflow preferences, commit settings, review options
Create a GitHub issue (or local issue with --local)
This skill should be used when creating, reading, or updating devloop plans in .devloop/plan.md, task tracking, progress logs, phase management, PR feedback
Create a devloop workflow plan with autonomous exploration and task breakdown
This skill should be used for integrating PR review comments back into devloop plan, parsing review feedback, addressing reviewer concerns
This skill should be used for Python idioms, type hints, async/await, pytest, Django, Flask, FastAPI, Python web frameworks, pandas, data processing
This skill should be used for React hooks, components, state management, performance, frontend TypeScript, Next.js, JSX/TSX, web UI components
Quick inline code review for devloop plan changes or PR diffs
Execute plan tasks via fresh-context subagents (swarm mode)
Execute plan tasks autonomously until completion
This skill should be used for OWASP, security review, authentication, XSS, SQL injection prevention, CSRF, input validation, secure coding, vulnerability scanning
Devloop commit and PR creation with validation for completed plan work
Configure the devloop statusline for Claude Code
This skill should be used for test coverage, test pyramid, unit/integration/E2E test design, TDD, BDD, mocking strategies, test doubles, test architecture
Production-ready Claude Code configuration with role-based workflows (PM→Lead→Designer→Dev→QA), safety hooks, 44 commands, 19 skills, 8 agents, 43 rules, 30 hook scripts across 19 events, auto-learning pipeline, hook profiles, and multi-language coding standards
Corca Workflow Framework — consolidated hooks and skill orchestration for structured development sessions
Development workflow automation including feature development, code quality, and PR management
AI-powered development workflow automation - Phase-based planning, implementation orchestration, preflight code quality checks with security scanning, ship-it workflow, and development principles generator for CLAUDE.md
End-to-end development workflow: design → draft-plan → orchestrate → review → pr-create → pr-review → pr-merge
Development workflow automation plugin: specify → open → execute pipeline with parallel research agents, hook-based guards, and PR state management
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
A curated marketplace of high-quality Claude Code plugins for professional development workflows.
# Add this marketplace
/plugin marketplace add Zate/cc-plugins
# Install plugins
/plugin install devloop # Workflow engine
/plugin install ctx # Persistent memory (optional but recommended)
/devloop:plan "add user authentication" # 1. Plan - explore and design
/devloop:run # 2. Build - implement autonomously
/devloop:ship # 3. Ship - commit and PR
# Repeat # 4. Start next feature
That's it. Claude does the work. You stay in control.
Need deep exploration? Use /devloop:plan --deep "topic" for comprehensive analysis.
Context getting heavy? Use /devloop:fresh && /clear && /devloop:run every 5-10 tasks.
New to plugins? Check out the Getting Started Guide for a complete walkthrough.
| Plugin | Description | Components |
|---|---|---|
| devloop | Development workflow engine with autonomous planning and execution | 13 commands, 7 agents, 15 skills |
| ctx | Persistent memory for Claude across sessions | 3 skills |
| security | OWASP ASVS-aligned security audits | 1 command, 17 agents |
| diagrams | Text-based diagram generation (SVG, Mermaid, Excalidraw, D2) | 6 skills |
| blog-writer | Conversational blog post creator | 1 command, 2 agents |
| wsl-clipboard-fix | WSL2 clipboard image paste fix | 1 skill, hooks |
The flagship plugin for professional software development. Simple workflow: plan, build, ship, repeat.
/plugin install devloop
# The workflow
/devloop:plan "add user authentication" # Plan with autonomous exploration
/devloop:run # Execute tasks autonomously
/devloop:ship # Commit and create PR
# Variations
/devloop:plan --deep "should we use OAuth?" # Deep exploration first
/devloop:plan --quick "fix the typo" # Skip planning for tiny tasks
/devloop:plan --from-issue 42 # Start from GitHub issue
Why devloop?
v3.18 Highlights:
/devloop:runRead the full devloop documentation →
Claude Code plugins extend your development environment with:
| Component | Purpose | Example |
|---|---|---|
| Commands | Custom slash commands | /devloop:quick Fix the bug |
| Agents | Specialized subagents | code-reviewer, test-generator |
| Skills | Domain knowledge | go-patterns, security-checklist |
| Hooks | Event automation | Auto-detect project type on session start |
| MCP Servers | External integrations | Connect to databases, APIs, services |
# Add marketplace
/plugin marketplace add Zate/cc-plugins
# Install specific plugin
/plugin install devloop
# Install from local path
/plugin install /path/to/cc-plugins/plugins/devloop
# Install from GitHub
/plugin install https://github.com/Zate/cc-plugins/plugins/devloop
# List installed plugins
/plugin list
# Check plugin details
/plugin info devloop
Want to contribute a plugin? We maintain high quality standards.
# Copy the template
cp -r templates/plugin-template plugins/your-plugin-name
# Update manifest
vim plugins/your-plugin-name/.claude-plugin/plugin.json
# Test locally
/plugin install /absolute/path/to/plugins/your-plugin-name
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claim