loop

Name: loop
Availability: InStock
Author: amotion-ai

Enforce a six-step development workflow with user approval at each gate.

Updated Apr 7, 2026

Search Tags:#automation #git #workflow #testing #development #project-management

Ready to run

npx skills add https://github.com/amotion-ai/botassist --skill loop-amotion-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: loop
Source: https://github.com/amotion-ai/botassist/tree/main/.claude/skills/loop
Command: npx skills add https://github.com/amotion-ai/botassist --skill loop-amotion-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent development practices cause missed quality checks, undocumented changes, and increased risk of bugs. This Skill guarantees that every ticket follows a complete, auditable process before code is merged.

Core Features & Use Cases

Six‑step workflow enforcement: triage, plan, implement, blast‑radius analysis, test, and pull‑request creation.
Gatekeeping with explicit user approval at each stage to prevent accidental skips.
Automated reporting: generates structured reports for triage, planning, implementation, blast radius, testing, and PR creation.
Applicable to any code change in the BotAssist repository, ensuring compliance with the team’s development policy.

Quick Start

Use the /loop command with a ticket ID or description to begin the guided workflow.

Frequently Asked Questions about loop

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

FAQPage Schema

How do I enforce a consistent development workflow for every ticket?▼

You can enforce a consistent development workflow by applying a structured six-step process—triage, planning, implementation, blast-radius analysis, testing, and pull-request creation—to every ticket, requiring explicit approval at each gate to prevent skipped quality checks.

What is blast-radius analysis in software development and when do I need it?▼

Blast-radius analysis evaluates the potential impact of code changes across a repository before testing. You need this systematic assessment step to identify undocumented changes and reduce the risk of introducing bugs before merging code.

How do I automate triage and pull-request creation for code changes?▼

Automate triage and pull-request creation by initiating a guided workflow with a ticket ID or description, which walks through each development phase sequentially and generates structured reports for both triage analysis and final PR creation.

Can I skip stages in an automated testing and implementation workflow?▼

No, you cannot skip stages because the workflow requires explicit user confirmation at each gate. This gatekeeping mechanism prevents accidental skips and ensures every code change passes triage, planning, implementation, blast-radius analysis, and testing.

Does this guided development workflow require specific CI commands or test suites?▼

The workflow integrates with your existing repository files, test suites, and CI commands to validate code changes during the testing phase. It applies to any code change within the repository, ensuring compliance with team development policies.

Why does inconsistent development practice increase bug risk?▼

Inconsistent development practices increase bug risk because they cause missed quality checks and undocumented changes. Enforcing a complete, auditable six-step process for every ticket guarantees that code is fully validated before merging.