moai-workflow-loop

Integrate LSP diagnostics, AST-grep scans, and test validation into Claude Code workflows.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/yslee5005/app-library --skill moai-workflow-loop-yslee5005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-workflow-loop
Source: https://github.com/yslee5005/app-library/tree/main/.claude/skills/moai-workflow-loop
Command: npx skills add https://github.com/yslee5005/app-library --skill moai-workflow-loop-yslee5005

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ralph Engine provides an automated feedback loop to continuously improve code quality by integrating LSP diagnostics, AST-grep scans, and test validation within Claude Code workflows.

Core Features & Use Cases

  • LSP Diagnostics after Write/Edit: Real-time feedback after edits to surface errors and warnings.
  • AST-grep Scanning: Structural checks for security and quality rules during development.
  • Loop Orchestration: Iterative fix/apply cycle with configurable stop conditions for zero-error goals.
  • Quick Start-like workflows: Trigger /moai commands to plan, run, and sync code quality improvements in CI/CD or local development.

Quick Start

Start a Ralph workflow loop with /moai:loop to begin automated feedback.

Frequently Asked Questions about moai-workflow-loop

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

FAQPage Schema
How do I automate LSP diagnostic feedback loops in Claude Code?

Automated LSP diagnostic feedback loops in Claude Code are orchestrated by triggering the /moai:loop command, which continuously applies edits and surfaces real-time errors until zero-defect conditions are met.

Can I use AST-grep scanning for structural code quality checks during development?

AST-grep scanning can be integrated into Claude Code workflows to perform structural security and quality rule checks during active development, ensuring continuous code quality validation.

How does iterative code quality validation with configurable stop conditions work?

Iterative code quality validation works by orchestrating a fix and apply cycle that repeatedly runs LSP diagnostics, AST-grep scans, and test validation until configured zero-error stop conditions are achieved.

Do I need any specific dependencies to run LSP-driven code quality loops?

No external dependencies are required to run LSP-driven code quality loops, as the Skill operates using built-in Ralph Engine components and Claude Code hooks for end-to-end loop orchestration.

What's the best way to integrate code quality checks into CI/CD pipelines?

Integrating code quality checks into CI/CD pipelines is best achieved by triggering /moai commands to plan, run, and sync automated LSP diagnostics and test validation workflows continuously.

Why are my automated code quality loops not stopping despite zero errors?

Automated code quality loops require properly configured stop conditions within the Ralph Engine orchestration; without explicit zero-defect thresholds, the iterative fix and apply cycle will continue running indefinitely.