Automated summary
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
Use after making commits on a yadm feature branch to quickly create a PR description.
Do not use if you are not working with yadm or if no commits have been made on the branch.
Security analysis
SafeThe 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
How this analysis is madeExamples
Run y-pr to create a pull request title and description for my current yadm branch.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:
- Not on main branch: If
current_branchequals "main", STOP and say: "Error: Cannot create PR from main. Create a feature branch first." - Has commits: If
commitsarray 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>
---
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/pr-title-and-description-generator-for-yadm-branch-mm8o5229/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/pr-title-and-description-generator-for-yadm-branch-mm8o5229' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/pr-title-and-description-generator-for-yadm-branch-mm8o5229/download' --output '.skill-downloads/pr-title-and-description-generator-for-yadm-branch-mm8o5229/SKILL.md.part' && mv '.skill-downloads/pr-title-and-description-generator-for-yadm-branch-mm8o5229/SKILL.md.part' '.skill-downloads/pr-title-and-description-generator-for-yadm-branch-mm8o5229/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/pr-title-and-description-generator-for-yadm-branch-mm8o5229/SKILL.md' && test -s '.skill-downloads/pr-title-and-description-generator-for-yadm-branch-mm8o5229/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/y-pr' && cp -R '.skill-downloads/pr-title-and-description-generator-for-yadm-branch-mm8o5229' '.claude/skills/y-pr'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/pr-title-and-description-generator-for-yadm-branch-mm8o5229'openskills read 'pr-title-and-description-generator-for-yadm-branch-mm8o5229'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/pr-title-and-description-generator-for-yadm-branch-mm8o5229/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.