skills.rest
samjonester
samjonesterCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

mozart-pr-description-routing

Route Mozart PR description generation to frontend, backend, or mixed validation skills.

5|1|Updated Nov 4, 2015
Search Tags:#frontend#routing#validation#backend#pr-description#diff-detection#mozart
One-click install
npx skills add https://github.com/samjonester/dotfiles --skill mozart-pr-description-routing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mozart-pr-description-routing
Source: https://github.com/samjonester/dotfiles/tree/main/personal/pi/skills/mozart-pr-description-routing
Command: npx skills add https://github.com/samjonester/dotfiles --skill mozart-pr-description-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route Mozart PR description generation to the correct validation skill based on changed files.

Core Features & Use Cases

  • Detect changed files and classify the diff into frontend, backend, or mixed categories.
  • Load and apply the corresponding validation skills to compose the PR description.
  • Enforce a clear routing line in the final PR description for auditability.

Quick Start

Provide a PR description request to Mozart and let it route to the appropriate validation steps.

Frequently Asked Questions about mozart-pr-description-routing

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

FAQPage Schema
How do I route PR descriptions to the correct validation checks based on changed files?▼

PR description routing automatically classifies file diffs into frontend, backend, or mixed categories and loads the corresponding validation skills to generate the appropriate PR description.

What is diff detection for PR description generation?▼

Diff detection for PR description generation analyzes changed files in a pull request, categorizes them as frontend, backend, or mixed, and applies matching validation rules to produce a structured summary with risks and impact.

How does PR description routing handle mixed frontend and backend changes?▼

PR description routing handles mixed changes by classifying the diff into a mixed category, loading both frontend and backend validation skills, and composing a unified PR description with all required validation sections.

Can I automatically enforce an audit trail in generated PR descriptions?▼

Yes, PR description routing enforces auditability by explicitly including a routing line in the final PR description, indicating which validation path was selected based on the detected file changes.

What sections are included in a routed PR description?▼

A routed PR description includes a summary of changes, a risks and impact section, and the required validation sections dictated by the loaded frontend, backend, or mixed validation skills.

Do I need external dependencies to classify diffs for PR description generation?▼

No, diff classification for PR description generation operates without external dependencies, using internal detection logic to categorize changed files and route them to the appropriate validation checks.

Related Skills

Explore More Content & Communication Skills→
byunghak-dablebyunghak-dable

github-pr-analyze

Analyze GitHub Pull Request changes and generate structural reports.

Community
Advanced
JeremyDev87JeremyDev87
31

requesting-code-review

Prepare structured PR descriptions with pre-flight checks and test evidence.

Community
Advanced
sauvalasauvala

writing-hookify-rules

Automate Hookify rule creation and syntax validation against predefined patterns.

Community
Intermediate
albinotonninaalbinotonnina
60

pr-description

Generate standardized pull request descriptions with required sections and template rules.

Community
Intermediate