pr-description-writer
PR Description Writer Skill
This skill generates clean, structured, production-ready Pull Request descriptions in Markdown format.
The user provides context about their PR (changes, bug, feature, architecture, etc). The skill determines or asks for the PR type and generates the correct template.
Proactive PR Detection
Before generating anything, always check if an open Pull Request already exists for the current branch using the gh CLI:
gh pr view --json number,title,url,body 2>/dev/null
- If a PR is found, note its number, current title, URL, and body. Inform the user that an open PR was detected and show the PR URL.
- If no PR is found (command exits non-zero), skip this step and proceed normally.
More from joyco-studio/skills
parallel-claudes
>
32markdown-content
>
31trace-audit
Analyze a Chrome DevTools Performance trace JSON file for performance anomalies, producing a structured audit report with critical issues, warnings, metrics, timeline hotspots, and actionable recommendations.
30joyco-lab
Use this skill whenever the user wants to isolate a piece of code, animation, or 3D experiment into a standalone JOYCO Lab experiment and publish it. Triggers include: \"isolate this\", \"publish this to the lab\", \"create a lab experiment\", \"extract this animation/effect/scene\", \"submit to JOYCO lab\", \"make this an experiment\". Also trigger when the user shows you a self-contained visual effect, animation, 3D scene, canvas sketch, or interactive component and wants to share or showcase it. Even if they don't say \"lab\" explicitly — if there's isolatable creative/technical code and a desire to share it, use this skill.
21thrash-report-analyzer
>
12webaudio
>
5