moai-workflow-loop

Automate LSP diagnostics, AST-grep scanning, and test validation loops for changed source files.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Jongsix/remote-claudecode --skill moai-workflow-loop-jongsix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-workflow-loop
Source: https://github.com/Jongsix/remote-claudecode/tree/main/.claude/skills/moai-workflow-loop
Command: npx skills add https://github.com/Jongsix/remote-claudecode --skill moai-workflow-loop-jongsix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill sets up an automated feedback loop for code changes so errors, warnings, and test failures are caught and resolved continuously instead of piling up.

Core Features & Use Cases

  • LSP-driven diagnostics: Checks changed files after edits and surfaces language-server errors with line-level context.
  • Loop orchestration: Repeats review and fixing cycles until completion criteria are satisfied or iteration limits are reached.
  • Quality validation: Combines AST-grep scanning, test execution, and coverage thresholds to support error-driven development and CI-style validation.
  • Use case: A developer uses this Skill to keep iterating on a feature until the codebase is clean, tests pass, and security or quality issues are addressed.

Quick Start

Use the moai-workflow-loop skill to automatically diagnose and fix code issues until the project reaches the configured completion conditions.

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 feedback for changed source files?

Continuous code quality feedback is automated by orchestrating an iterative loop that applies LSP diagnostics, AST-grep scanning, and test validation to changed source files until completion criteria are met or iteration limits are reached.

What is an LSP-driven diagnostic loop for iterative development?

An LSP-driven diagnostic loop is an automated process that repeatedly checks changed files using language server protocol diagnostics, surfaces line-level errors, and applies fixes iteratively to support error-driven development.

Does AST-grep scanning work with LSP diagnostics for code validation?

AST-grep scanning works with LSP diagnostics by combining syntax tree pattern matching with language server error detection, creating a comprehensive quality validation mechanism within an automated iterative feedback loop.

How do I set up an automated feedback loop for test failures and code warnings?

An automated feedback loop for test failures and warnings is set up by configuring loop state tracking and completion checks that repeatedly execute tests, scan with AST-grep, and apply fixes until the codebase is clean.

What happens when the code quality fixing loop reaches the iteration limit?

When the code quality fixing loop reaches the iteration limit, it halts the automated review and fixing cycles, leaving any remaining errors or test failures unresolved for manual inspection.

Can I use diagnostic-driven repairs across multiple supported languages?

Diagnostic-driven repairs can be applied across supported languages by leveraging LSP servers that provide language-specific diagnostics, enabling the iterative fixing loop to address errors in diverse codebases.