moai-workflow-loop

Automate the Ralph Engine workflow loop with LSP diagnostics and AST-grep scanning.

1|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/GoosLab/moai-rank --skill moai-workflow-loop-gooslab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-workflow-loop
Source: https://github.com/GoosLab/moai-rank/tree/main/.claude/skills/moai-workflow-loop
Command: npx skills add https://github.com/GoosLab/moai-rank --skill moai-workflow-loop-gooslab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ralph Engine automates an automated feedback loop with LSP diagnostics and AST-grep integration to continuously improve code quality.

Core Features & Use Cases

  • Real-time LSP diagnostics after Write/Edit operations to surface issues early
  • AST-grep scanning for security and quality pattern detection
  • Iterative feedback loop with post-tool hooks and loop control to drive automated fixes
  • CI/CD friendly workflows and plan-run-sync patterns for reproducible quality checks

Quick Start

Plan and run a Ralph loop on your project with /moai:loop to begin automated diagnostics and fixes.

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 continuous code quality loops with LSP diagnostics and AST-grep?

Automated code quality loops use the Ralph Engine to run post-tool hooks, scanning code with AST-grep and validating via LSP diagnostics to iteratively surface and fix issues. This creates a continuous feedback cycle during feature development or CI/CD pipelines.

What is the best way to set up automated feedback loops for error-driven development?

Error-driven development loops require a configured project with a ralph.yaml setup and accessible LSP servers. You execute the loop using specific commands to begin automated diagnostics, enabling iterative fixes based on real-time language server feedback.

Can I integrate AST-grep scanning and test validation into CI/CD pipelines?

AST-grep scanning and test validation integrate into CI/CD pipelines using plan-run-sync patterns. This workflow drives reproducible quality checks by combining security pattern detection with automated test validation during the loop.

Do I need a specific project configuration to run Ralph Engine loops?

Running Ralph Engine loops requires a configured project with Claude-enabled loop commands, a ralph.yaml setup, and accessible LSP servers and sg rules. These components drive the automated feedback necessary for iterative code improvements.

Why use AST-grep for security and quality pattern detection in an automated loop?

AST-grep provides structural code scanning to detect security and quality patterns within automated loops. It surfaces targeted issues early, guiding the iterative feedback loop to apply automated fixes alongside real-time LSP diagnostics.

When should I avoid running automated code quality loops?

Avoid running automated code quality loops when the project lacks accessible LSP servers or AST-grep rules. Without the required ralph.yaml configuration and language server diagnostics, the iterative fixing loop cannot function properly.