branch-pr-workflow

Create a feature or refactor branch from dev and open a PR after passing delivery gates.

5|1|Updated May 9, 2026

Search Tags:#git #workflow #pre-commit #branch #pr #dev #quality-checks

Ready to run

npx skills add https://github.com/ql-link/LinkRag --skill branch-pr-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: branch-pr-workflow
Source: https://github.com/ql-link/LinkRag/tree/main/.ai/skills/branch-pr-workflow
Command: npx skills add https://github.com/ql-link/LinkRag --skill branch-pr-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

当用户认为当前模块代码实现完毕，且当前分支应为 dev，需要从 dev 基于当前修改创建规范分支、提交并发起合并到 dev 的 GitHub PR 时使用。本 Skill 作为交付链的收口点，在建分支/提 PR 之前执行收口门槛：测试未全绿、契约文档未同步、acceptance 未提升时将拒绝收口。这个工作流确保变更在合并回开发分支之前经过严格的验证和对齐，以降低回滚风险并提升交付质量。

Core Features & Use Cases

Delivery gate enforcement: 从 dev 派生规范分支，并在通过前置条件后创建指向 dev 的合并请求，确保变更可审计和可追踪。
Pre-checks before PR: 自动执行测试、契约文档同步与 acceptance 指标对齐等硬性门槛，只有全部通过才允许继续收口。
适用场景: 适用于“从 dev 新建分支、把当前修改提 PR、实现完成后创建 feature/refactor 分支并 PR”等交付收口场景，确保交付链末端的可控性。

Quick Start

在 dev 分支上完成修改后，执行本技能以创建规范分支并向 dev 提交 PR。

Frequently Asked Questions about branch-pr-workflow

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

FAQPage Schema

How do I create a feature branch from dev and open a PR with pre-commit checks?▼

To create a feature branch from dev and open a PR, the workflow isolates current dev changes into a named branch and enforces CI gate checks before submitting the merge request back to dev.

What happens if my tests fail before opening a pull request?▼

If tests fail before opening a pull request, the delivery gate enforcement blocks the PR creation, ensuring that only fully validated changes with green tests are merged back into the dev branch.

Can I enforce contract documentation synchronization before merging to dev?▼

Yes, you can enforce contract documentation synchronization before merging to dev; the workflow runs pre-checks to verify that documentation is aligned before allowing the PR to proceed.

When do I need to use a branch and PR workflow for feature delivery?▼

You need a branch and PR workflow for feature delivery when you must isolate current changes on dev into a separate branch to enforce quality checks, acceptance improvements, and auditability before merging.

Why does branch naming matter when submitting a PR from a feature branch?▼

Branch naming matters when submitting a PR because the workflow enforces naming conventions to ensure traceability and standardized delivery tracking within the development cycle.

Does the PR workflow require acceptance improvements before merging?▼

Yes, the PR workflow requires acceptance improvements before merging; the delivery gate explicitly checks for acceptance metric alignment and rejects the PR if these improvements are not met.