PR Title and Description Generator for Yadm Branch

VerifiedSafe

Generates a pull request title and description for a yadm branch. It gathers context, validates that the branch is not main and has commits, then outputs a formatted title and body following specific rules. Helps create consistent, ready-to-use PRs for dotfile changes.

Sby Skills Guide Bot
DevelopmentIntermediate
806/2/2026
Claude Code
#pr-generation#yadm#git-workflow#pull-request#branch-management

Recommended for

Our review

Generates a pull request title and description for a yadm repository branch based on gathered context.

Strengths

  • Automates PR formatting with strict title and body rules
  • Checks preconditions to avoid invalid PRs (e.g., on main branch, no commits)
  • Outputs ready-to-copy text with clear structure

Limitations

  • Only works with yadm repositories and the specific gather script
  • Requires the gather script to be present and executed
  • Does not actually submit the PR, only generates the text
When to use it

Use after making commits on a yadm feature branch to quickly create a PR description.

When not to use it

Do not use if you are not working with yadm or if no commits have been made on the branch.

Security analysis

Safe
Quality score90/100

The skill only runs a local Python script to gather context and does not perform any dangerous operations like remote code execution or file deletion. There are no security concerns in the instruction itself.

No concerns found

Examples

Generate PR for current yadm branch
Run y-pr to create a pull request title and description for my current yadm branch.
Create PR summary after commits
I've made some commits on a yadm feature branch. Use y-pr to generate the PR description.

name: y-pr description: Generate PR title and description for yadm branch allowed-tools:

  • Bash(yadm *)
  • Bash(python *)

Generate PR for Yadm Branch

Gather Context

Run the gather script:

python scripts/gather_context.py

Preconditions

Check these in the JSON output BEFORE proceeding:

  1. Not on main branch: If current_branch equals "main", STOP and say: "Error: Cannot create PR from main. Create a feature branch first."
  2. Has commits: If commits array is empty, STOP and say: "Error: No commits found. Make commits before creating a PR."

Title Format

  • Under 70 characters
  • Imperative mood (e.g., "Add feature" not "Added feature")
  • No period at end
  • Summarize the main change

Body Format

Use this exact structure:

## Summary

- <bullet 1: main change, start with verb>
- <bullet 2: supporting change or context>
- <optional bullet 3-4 if needed>

Rules:

  • Each bullet starts with a verb (Add, Fix, Update, Remove, etc.)
  • Focus on WHAT and WHY, not HOW
  • No file paths unless the file itself is the feature
  • Do not include any watermark, attribution, or "Generated by" text

Output

Output in this exact format for copy/paste:

---
**Title:**
<title here>

**Description:**
<body here>
---
Related skills