ralph-val

To validate code implementation against plan requirements, the skill parses plan documents to extract automated verification steps, including file checks, command executions, and content pattern matching. It reports a PASS or FAIL verdict based on whether the code satisfies the success criteria.

Automated plan adherence verification in CI/CD is the process of checking if code implementations meet predefined success criteria from a plan document. It executes file checks, runs commands, and matches content patterns to prevent merging code that fails to meet specifications.

You can check for specific file existence and output patterns in a GitHub worktree by using a validation skill that parses your plan document. It automatically executes these predefined checks against the implemented code within the specified worktree directory and posts the results as a GitHub comment.

Yes, the validation skill works with GitHub Actions and operates on a given issue number. It processes the implementation within a specified worktree and posts the PASS or FAIL validation results directly as a GitHub comment.

Yes, you can use a custom plan document path for code review validation. The skill accepts an optional plan document path argument alongside the required issue number to extract and execute the specific automated verification steps.

The limitations of automated code validation against plan requirements include its reliance on predefined checks within the plan document. It can only verify explicit success criteria like file existence, command execution, and content patterns, meaning implicit requirements or complex logic errors might not be caught.