Agent Skills
› codeaholicguy/ai-devkit
› dev-pr
dev-pr
GitHub用于将已提交的特性分支发布至代码审查。该技能负责验证仓库状态、拉取最新代码、变基解决冲突、安全推送并创建或更新GitHub/GitLab等平台的PR/MR请求,同时报告审查链接及验证结果。
触发场景
用户希望同步并推送代码以发起代码审查
用户要求更新现有的代码评审请求
需要将特性分支发布到远程仓库供他人Review
安装
npx skills add codeaholicguy/ai-devkit --skill dev-pr -g -y
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, andgit 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-leaseonly 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 -sbgit branch --show-currentgit 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/mainonly 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:
- Review URL and state
- Branch and HEAD SHA
- Validation commands and exit codes
- Push mode, including whether
--force-with-leasewas used - Risks, follow-ups, or blockers
版本历史
- d4caf56 当前 2026-07-05 15:22


