devloop

Use 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>

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

3 hooks across 3 events