# Pr Workflow

> Create and repair UniRL pull requests. Use when creating a PR, editing a PR body, responding to PR Body or Semantic Pull Request CI failures, running gh pr create, or when the user mentions PR body, pull request template, body check, title check, or pull request formatting.

- Skill: `tencent-hunyuan/pr-workflow-2` (Agent Skill)
- Install (CLI): `npx skillmds@latest add tencent-hunyuan/pr-workflow-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tencent-hunyuan/pr-workflow-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: tencent-hunyuan (https://skillmd.com/u/tencent-hunyuan)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tencent-hunyuan/pr-workflow-2

---


# PR Workflow

## Before Creating Or Updating A PR

1. Read `.github/pull_request_template.md`, `.github/workflows/pr-body.yml`, and `.github/workflows/semantic-pull-request.yml` from the current branch.
2. Inspect the full diff against the intended base branch, not just the latest commit.
3. Check for overlapping open PRs or issues when the user is asking to publish a substantive change.
4. Do not include unrelated local files, generated artifacts, datasets, checkpoints, credentials, or outputs.

## Title

Use the Semantic Pull Request types allowed by `.github/workflows/semantic-pull-request.yml`:

`fix`, `feat`, `docs`, `test`, `refactor`, `build`, `ci`, `chore`, `perf`, `revert`.

Prefer a concise title in the form `type(scope): summary` when a scope is helpful, otherwise `type: summary`.

## Body

Start from `.github/pull_request_template.md` and fill it with reviewer-facing content.

Required by the body check:

- `## Summary` must contain visible, non-comment text explaining what changed and why.
- `## Test Plan` must contain visible, non-comment text with exact validation commands/jobs, or `Not run; reason: ...`.

Recommended:

- Use `N/A` for sections that do not apply.
- Mention compatibility risks for config, checkpoint, data format, API, resource, or migration changes.
- Mention AI assistance and duplicate-work checks when relevant.
- Keep the body concise; do not produce a file-by-file changelog.

## Fixing PR Body Failures

If the `PR Body / Validate PR body sections` check fails:

1. Read the failure message.
2. Ensure the PR is not relying on HTML comments or untouched template examples as content.
3. Add real text under `## Summary` and `## Test Plan`.
4. Do not solve failures by weakening the workflow unless the user explicitly asked to change policy.