Agent Skills › codeaholicguy/ai-devkit › dev-pr

dev-pr

GitHub

用于同步、推送功能分支并创建或更新代码审查请求。自动执行上下文验证、远程拉取、变基合并及冲突解决，确保分支安全推送后生成包含摘要、验证结果和风险说明的PR/MR描述。

skills/dev-pr/SKILL.md codeaholicguy/ai-devkit

Trigger Scenarios

用户希望将已完成提交的功能分支推送到远程仓库以发起代码审查用户需要更新现有的Pull Request或Merge Request

Install

npx skills add codeaholicguy/ai-devkit --skill dev-pr -g -y

More Options

Use without installing

npx skills use codeaholicguy/ai-devkit@dev-pr

指定 Agent (Claude Code)

npx skills add codeaholicguy/ai-devkit --skill dev-pr -a claude-code -g -y

安装 repo 全部 skill

npx skills add codeaholicguy/ai-devkit --all -g -y

预览 repo 内 skill

npx skills add codeaholicguy/ai-devkit --list

SKILL.md

Frontmatter

{
    "name": "dev-pr",
    "description": "AI DevKit · Publish a ready feature branch for review. Use when the user wants to sync, push, and open or update a code review request on GitHub, GitLab, or another Git host."
}

Dev PR

Publish an already-reviewed branch for code review. Keep this separate from commit creation: if the branch has uncommitted changes, stop and ask the user to run the commit workflow first.

Contract

Verify repository context with git status -sb, git branch --show-current, and git remote -v.
Confirm the branch is not the base branch and has committed changes to publish.
Fetch the remote before comparing or rebasing.
Rebase the feature branch onto the latest remote base branch before push/review.
Resolve conflicts carefully, preserving intended behavior, then rerun relevant validation.
Push safely. Use --force-with-lease only when a rebase rewrote an already-pushed branch.
Open or update the host's review request: PR, merge request, or equivalent.
Report review URL, branch, HEAD SHA, validation results, push mode, and risks.

Publish Workflow

Inspect local context:
- git status -sb
- git branch --show-current
- git remote -v
If uncommitted changes exist, stop. Do not stage, amend, squash, or commit in this skill.
Identify the remote and base branch from repo conventions, upstream config, or user instruction; default to origin/main only when that matches the repo.
Fetch the remote, inspect the delta, and rebase onto the remote base branch.
If conflicts occur, inspect conflicted files and git diff, resolve minimally, validate when useful, git add, then continue the rebase. Stop if the correct resolution is unclear.
Run relevant validation for the changed surface.
Push:
- First push: set upstream.
- Normal update: plain push.
- Rebased already-pushed branch: --force-with-lease.
Open or update the review request using the host's tool/API/UI (gh, glab, forge CLI, web UI, or project-specific workflow).
Write a concise review description. Include enough for reviewers to understand:
- Summary: what changed, why, and how.
- Validation: how it was verified.
- Risks: notable risks or "none known".
Report: