skills.rest
arusinova
arusinovaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

write-pr

Generate Conventional Commits PR titles and structured PR bodies for tldraw.

Updated Aug 27, 2026
Search Tags:#templates#documentation#pr#code-review#git-workflow#pull-request#conventional-commits
One-click install
npx skills add https://github.com/arusinova/annarusinova-platform --skill write-pr-arusinova
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-pr
Source: https://github.com/arusinova/annarusinova-platform/tree/main/.claude/skills/write-pr
Command: npx skills add https://github.com/arusinova/annarusinova-platform --skill write-pr-arusinova

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafting consistent PR titles and bodies can be time-consuming and error-prone. This Skill provides a structured approach to generate conventional PR content that aligns with project guidelines.

Core Features & Use Cases

  • Semantic PR titles follow the Conventional Commits format to clearly describe the change type and scope.
  • Scope handling: optional scope to contextualize the affected area, improving traceability in reviews.
  • PR body template: includes sections such as Description paragraph, Change type, Test plan, Release notes, API changes, and Related issues to standardize reviews.
  • Use cases: produce ready-to-submit titles and bodies for new PRs, update existing PR titles or descriptions, and respond to /pr prompts with guided content.

Quick Start

Provide a semantic PR title and a fully formed PR body using the templates when creating or updating a PR.

Frequently Asked Questions about write-pr

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

FAQPage Schema
How do I write a pull request title using Conventional Commits?▼

To write a pull request title using Conventional Commits, apply a semantic format that clearly describes the change type and includes an optional scope to contextualize the affected area for better review traceability.

What should be included in a structured PR body template?▼

A structured PR body template should include sections for a Description paragraph, Change type, Test plan, Release notes, API changes, and Related issues to standardize code reviews and project documentation.

How do I generate a PR description for a new pull request?▼

You generate a PR description for a new pull request by providing a semantic PR title and applying a structured PR body template, producing ready-to-submit content that aligns with project guidelines.

Can I update an existing PR title and description with conventional commit formats?▼

Yes, you can update an existing PR title and description by applying semantic title formats that follow Conventional Commits and regenerating the structured PR body sections to match project guidelines.

Does this PR template work for repositories outside of tldraw?▼

The PR template automates compliant PR content creation specifically aligned with the tldraw repository guidelines, applying its required semantic title formats and structured body sections for repository workflows.

Why do I need a standardized PR body with specific sections like Release notes and API changes?▼

You need a standardized PR body with specific sections like Release notes and API changes to standardize reviews, ensure traceability, and maintain consistent project documentation across repository workflows.

Related Skills

Explore More Software Engineering Skills→
damilola-elegbede-orgdamilola-elegbede-org

pr

Generate pull request titles and descriptions from commit changes.

Official
Intermediate
cofadecofade
16

analyze-pr

Analyze GitHub Pull Requests and generate manual test plans.

Community
Advanced
Doyajin174Doyajin174
1

changelog-generator

Convert git commit history into categorized Markdown release notes.

Community
Intermediate
yamato0811yamato0811

pull-request-creator

Summarize Git branch diffs and draft a pull request targeting develop.

Community
Basic