skills.rest
bostonaholic
bostonaholicCOMMUNITY
Explore all skills by this author →
Website𝕏@bostonaholicGitHub

team-pr

Automate pull request creation with branch pushing, changelog updates, and screenshot attachments.

8|1|Updated Mar 28, 2026
Search Tags:#automation#workflow#changelog#devops#pull request#github
One-click install
npx skills add https://github.com/bostonaholic/team --skill team-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-pr
Source: https://github.com/bostonaholic/team/tree/main/skills/team-pr
Command: npx skills add https://github.com/bostonaholic/team --skill team-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the end-to-end pull request lifecycle, eliminating manual overhead in branch management, changelog updates, and screenshot documentation.

Core Features & Use Cases

  • Automated PR Lifecycle: Automatically pushes branches, opens draft PRs, and links companion PRs in multi-repo environments.
  • Integrated Documentation: Updates CHANGELOG.md based on commit history and embeds verified UI screenshots directly into the PR body.
  • Use Case: After completing a feature implementation, use this skill to instantly open a draft PR, update the project changelog, and attach relevant UI screenshots without manual intervention.

Quick Start

Use the team-pr skill to open a draft pull request for the current worktree and update the project changelog.

Frequently Asked Questions about team-pr

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

FAQPage Schema
How do I automate pull request creation with changelog updates and UI screenshots?▼

Automating pull request creation involves pushing branches, opening draft PRs, updating the changelog from commit history, and embedding UI screenshots, streamlining the end-to-end PR lifecycle without manual overhead.

What is the best way to manage companion pull requests in a multi-repo development workflow?▼

Managing companion pull requests in a multi-repo workflow requires automatically pushing branches and linking related draft PRs across repositories to maintain consistent PR descriptions and lifecycle tracking.

How do I automatically generate a CHANGELOG.md update from my commit history before opening a GitHub PR?▼

Automatically generating a CHANGELOG.md update analyzes conventional commit history to produce formatted changelog entries, directly integrating the documentation into the pull request body.

Can I attach UI screenshots directly to a draft PR body using GitHub-native assets?▼

Attaching UI screenshots directly to a draft PR body uses GitHub-native asset attachment, embedding verified visual documentation into the pull request description automatically.

Does automated PR creation support conventional commit formatting and ticket lifecycle tracking?▼

Automated PR creation supports conventional commit formatting and ticket lifecycle tracking, applying these requirements to multi-repo development workflows for consistent PR descriptions.

When should I not use an automated pull request workflow for branch management?▼

You should avoid automated pull request workflows for branch management if your project lacks conventional commit formatting or does not require consistent changelog updates and UI verification.

Related Skills

Explore More Software Engineering Skills→
GGPromptsGGPrompts
147

merge

Merge feature branches into main and clean up worktrees using Git.

Community
Advanced
oalansilvaoalansilva

release-notes-drafter

Draft release notes from merged PRs and commits.

Community
Intermediate
khapn-2933khapn-2933

tkm:git

Automate git staging, committing, pushing, and pull requests with conventional commits.

Community
Advanced
NodeJSmithNodeJSmith
1

mine.ship

Commit, push, and create draft pull requests on GitHub and Azure DevOps.

Community
Advanced