What problem does it solve?
Different GitHub organizations follow wildly different pull request conventions — from checklist items and Changes block formats to data sourcing habits and QA section wording. Applying the wrong brand's format produces PRs that fail local review, while manually adapting each PR wastes maintainer time and introduces inconsistency.
Core Features & Use Cases
- Auto-brand detection: Identifies the target brand (Madison Reed, Kyonax, or generic fallback) from the git remote URL or user override, then loads the exact format and data-source conventions for that brand.
- Brand-aware PR generation: Drafts complete PR bodies with the correct checklist items, Changes pattern (flat list vs themed subsections), Technical Details variant, Testing Coverage layout, QA heading wording, and Documentation vocabulary.
- Validation and maintenance: Validates existing PR text against brand rules and helps onboard new brands by capturing conventions into reusable rule files.
Quick Start
Use the pr-scribe skill to draft a pull request body for the current repository by simply asking it to write the PR description, and it will automatically detect the brand and apply the correct conventions.