mozart-validate

Automate end-to-end validation of Mozart PRs with scripted checks and comments.

5|1|Updated Nov 4, 2015
One-click install
npx skills add https://github.com/samjonester/dotfiles --skill mozart-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mozart-validate
Source: https://github.com/samjonester/dotfiles/tree/main/personal/pi/skills/mozart-validate
Command: npx skills add https://github.com/samjonester/dotfiles --skill mozart-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual validation of Mozart PRs is time-consuming and error-prone; this Skill automates the runtime validation workflow by checking out the PR in a dedicated WTP worktree, reading the PR description to derive validation steps, classifying changes as BE/FE/GQL, building validation scripts (Rails runner, GQL queries, or Playwright), capturing evidence, and drafting a top-level PR comment with results.

Core Features & Use Cases

  • PR metadata extraction and safe worktree checkout (WTP) to avoid touching main branches
  • Description-driven validation: classify changes as BE/FE/GQL and generate targeted scripts
  • Multi-path validation: Rails runner for BE, GraphQL queries for GQL, Playwright UI checks
  • Evidence capture and automated PR commentary to summarize results

Quick Start

Run the mozart-validate workflow against a target PR to automatically validate changes and report results.

Frequently Asked Questions about mozart-validate

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

FAQPage Schema
How do I automate pull request validation for Rails, GraphQL, and Playwright changes?

Automate pull request validation by orchestrating PR checkout, classifying changes as BE, GQL, or FE, and generating targeted Rails runner, GraphQL query, or Playwright scripts to execute and capture validation evidence automatically.

What is the best way to run validation scripts in an isolated workspace without affecting main branches?

Use WTP worktree checkout to isolate PR validation in a dedicated workspace. This ensures safe PR checkout without touching main branches while running scripted validations and collecting evidence.

How does description-driven PR validation classify and generate scripts for different code changes?

Description-driven PR validation reads the PR description to classify changes as BE, FE, or GQL. It then generates appropriate validation scripts using Rails runner for backend, GraphQL queries for GQL, or Playwright for frontend UI checks.

Can I automatically post validation results and evidence as a PR comment?

Yes, automated PR commentary drafts a top-level PR comment summarizing validation results. It captures evidence from the executed Rails, GraphQL, and Playwright scripts and posts the summary directly to the pull request.

Does this PR validation workflow support backend, frontend, and GraphQL testing paths simultaneously?

Yes, the PR validation workflow supports multi-path validation across backend, frontend, and GraphQL classifications. It builds and runs Rails runner, Playwright, and GraphQL query scripts concurrently to validate all change types.

Why does manual PR validation fail to scale for complex Rails and Playwright codebases?

Manual PR validation is time-consuming and error-prone for complex codebases. Automating the runtime validation workflow via script generation, evidence capture, and automated commentary ensures consistent, end-to-end validation across all PR classifications.