y-pr-title

Generate a concise PR title from the current yadm branch context.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/salimhamed/dotfiles --skill y-pr-title
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: y-pr-title
Source: https://github.com/salimhamed/dotfiles/tree/main/.claude/skills/y-pr-title
Command: npx skills add https://github.com/salimhamed/dotfiles --skill y-pr-title

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of consistent PR titles for yadm-managed dotfiles, reducing manual title crafting and ensuring uniform phrasing across commits.

Core Features & Use Cases

  • Automated PR Title Generation: Builds concise, action-oriented titles from the current yadm branch context.
  • Context-Rich Output: Uses current branch, base branch, commit list, diff stats, and changed files to inform title generation.
  • Use Case: When preparing a PR for a yadm-based dotfiles update, run this skill to produce a ready-to-copy PR title that reflects the changes.

Quick Start

Run the gather script to generate a PR title for the current yadm branch: python scripts/gather_context.py The script outputs a JSON object with current_branch, base_branch, commits, diff_stat, and files_changed, which you can feed into a title generator to produce the final title.

Frequently Asked Questions about y-pr-title

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

FAQPage Schema
How do I generate a PR title for my yadm-managed dotfiles branch?

Generating PR titles for yadm dotfiles branches involves running a Python script that gathers current branch, base branch, commits, diff stats, and changed files into a JSON object for automated title generation.

Can I automate consistent PR title creation for yadm dotfiles workflows?

Automating PR title creation for yadm dotfiles workflows is achieved by analyzing branch comparisons and change reviews to produce consistent, action-oriented titles without manual crafting.

What context is needed to generate a PR title for a yadm branch?

Generating a PR title for a yadm branch requires current branch, base branch, commits, diff stats, and changed files, which the script collects into a JSON object to inform the title generation.

Does this PR title generation approach work with standard git branches or only yadm?

This PR title generation approach targets yadm-based dotfiles workflows specifically, reading yadm branch comparisons and change reviews to produce structured context for title generation.

Why should I use an automated script for yadm pull request titles instead of writing them manually?

Using an automated script for yadm pull request titles ensures consistent phrasing across dotfiles updates by building structured context from commits and diff stats, eliminating manual title crafting.