moai-workflow-loop

Automated code error fixing loops with LSP and AST-grep are orchestrated by applying PostToolUse and Stop hooks to continuously diagnose, fix, and validate code quality until criteria are met. This workflow requires a Ralph configuration file to coordinate iterative self-correction.

An automated feedback loop for code quality using LSP diagnostics continuously collects real-time errors after edits and applies AST-based security checks to flag issues. This mechanism enables iterative self-correction by validating code quality automatically during development.

Yes, running LSP diagnostics and AST-grep scanning requires a Ralph configuration file named ralph.yaml. You also need an LSP client, AST-grep rules, and Stop or PostToolUse hooks to orchestrate loop iterations within the Claude Code environment.

To start a workflow loop to continuously diagnose and fix code errors, issue Claude Code commands like /moai:loop to begin iterative diagnostics, then use /moai:fix to apply fixes as issues are found. Monitor progress and adjust configuration in ralph.yaml as needed.

Yes, AST-grep security checks can be integrated with Claude Code through PostToolUse and Stop hooks. These hooks coordinate edits and trigger automatic fix iterations, applying AST-based quality checks after LSP diagnostics identify real-time errors.

Iterative code quality validation using AST-grep rules is limited to environments using the Ralph Engine and requires specific hook configurations. It relies on LSP client availability and properly defined AST-grep rules to flag issues during the automated self-correction loop.