When should I not use this skill?

Only on explicit request; skip in routine implementation discussions.

What should be included in the PR description?

A clear summary of changes, the context and motivation, any breaking changes, and UI screenshots if applicable.

What is in the PR template?

A checklist including feature or bug fix, unit tests pass, and manual testing completed.

create-pr

npx machina-cli add skill gologo13/agent-skills/create-pr --openclaw

Files (1)

SKILL.md

902 B

Create PR

Overview

Create a well-structured pull request with proper description, labels, and reviewers.

Steps

Prepare branch
- Ensure all changes are committed
- Push branch to remote
- Verify branch is up to date with main
Write PR description
- Summarize changes clearly
- Include context and motivation
- List any breaking changes
- Add screenshots if UI changes
Set up PR
- Create PR with descriptive title
- Add appropriate labels
- Assign reviewers
- Link related issues

PR Template

Feature A
Bug fix B
Unit tests pass
Manual testing completed

Source

git clone https://github.com/gologo13/agent-skills/blob/main/skills/create-pr/SKILL.mdView on GitHub

Overview

This skill guides you to create a well-structured pull request by preparing the branch, writing a descriptive summary, and configuring labels and reviewers. It emphasizes linking related issues and documenting context and motivation to speed reviews and reduce back-and-forth.

How This Skill Works

First, prepare the branch by ensuring all changes are committed, pushing to remote, and updating it with main. Then write a PR description that summarizes changes, includes context and motivation, and notes any breaking changes or UI considerations. Finally, set up the PR with a descriptive title, add appropriate labels, assign reviewers, and link related issues; follow the PR template checklist to enforce consistency.

When to Use It

When merging a feature branch into main after completing work
Before releasing a release candidate to QA or stakeholders
When changes touch the UI and screenshots help communicate visuals
When there are breaking changes or API/behavior shifts to document
When traceability and reviewer assignment improve code quality

Quick Start

Step 1: Prepare branch — commit changes, push to remote, and ensure it is up to date with main
Step 2: Write PR description — summarize changes, add context and motivation, note breaking changes
Step 3: Create PR — craft a descriptive title, add labels, assign reviewers, and link related issues

Best Practices

Ensure the branch is committed and up to date with main before creating the PR
Write a concise but complete PR description with changes, context, and motivation
Clearly list any breaking changes and include UI screenshots if applicable
Use a descriptive PR title and assign relevant labels
Assign reviewers and link related issues for traceability

Example Use Cases

Add user profile page and attach UI screenshots to the PR description
Fix login bug under edge-case conditions and document test coverage
Refactor data access layer to improve performance with minimal UI impact
Update unit tests to cover newly added edge cases and feature flags
Remove deprecated feature flag and link to the related issue

Frequently Asked Questions

Add this skill to your agents