pr-workflow

Create and repair UniRL pull request bodies and titles for GitHub review workflows.

890|61|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/Tencent-Hunyuan/UniRL --skill pr-workflow-tencent-hunyuan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-workflow
Source: https://github.com/Tencent-Hunyuan/UniRL/tree/main/.cursor/skills/pr-workflow
Command: npx skills add https://github.com/Tencent-Hunyuan/UniRL --skill pr-workflow-tencent-hunyuan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation and repair of UniRL pull requests by keeping PR bodies, titles, and formatting aligned with the repository’s expectations.

Core Features & Use Cases

  • PR Creation Guidance: Helps draft new pull request bodies that match the project template and review standards.
  • PR Repair and Cleanup: Fixes existing PR bodies when body checks, title checks, or semantic pull request CI fail.
  • Workflow Support: Assists with common GitHub pull request tasks such as preparing changes for gh pr create and resolving formatting issues before merge.
  • Use Case: Use this Skill when a developer needs to update a PR description, respond to CI feedback, or make a pull request ready for review.

Quick Start

Ask the AI to create or repair a UniRL pull request body so it matches the repository template and passes PR validation.

Frequently Asked Questions about pr-workflow

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

FAQPage Schema
How do I fix a pull request body when semantic PR CI fails on GitHub?

To fix a pull request body when semantic PR CI fails, the PR body and title must be aligned with the repository's specific template and formatting rules. This ensures the pull request passes validation and becomes ready for review.

How do I create a pull request body that matches my repository template?

Creating a pull request body that matches your repository template requires formatting the description according to the project's specific review standards and gh pr create-oriented rules. This alignment ensures the PR meets the required validation checks before merge.

Why does my GitHub pull request title check keep failing?

A GitHub pull request title check fails when the title does not comply with the repository's semantic pull request validation rules. Repairing the title involves applying the correct formatting and semantic structure expected by the project's CI workflow.

Can I use this workflow to prepare changes for gh pr create?

Yes, you can use this workflow to prepare changes for gh pr create by formatting the pull request body and title according to the repository template. This ensures the created pull request meets formatting standards before submission.

What is the best way to resolve pull request formatting issues before merge?

The best way to resolve pull request formatting issues before merge is to repair the PR body and title to match the repository's template and review feedback. This resolves formatting checks and ensures CI validation passes cleanly.