GitHub 推送与 PR 管理自动化工具 - 安全推送、自动创建/更新 PR

push by odysseus0/symphony

132 周安装量

55 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/odysseus0/symphony --skill push

自动化开发运维版本控制

🇨🇳中文介绍

推送

前提条件

gh CLI 已安装并可在 PATH 中找到。
在此仓库中执行 GitHub 操作时，gh auth status 命令成功。

目标

安全地将当前分支的更改推送到 origin。
如果分支不存在 PR，则创建一个；否则更新现有的 PR。
当远程分支已更新时，保持分支历史记录整洁。

步骤

识别当前分支并确认远程状态。
推送前运行本地验证（make -C elixir all）。

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

相关 Skills

FlyClaw：零登录航班聚合查询工具，Python实现多源航班信息与价格搜索

4,000,000 周安装

Vercel React 最佳实践指南 | 58条Next.js性能优化规则与代码重构

281,000 周安装

agent-browser 浏览器自动化工具 - Vercel Labs 命令行网页操作与测试

155,300 周安装

Azure Data Explorer (Kusto) 查询技能：KQL数据分析、日志遥测与时间序列处理

128,400 周安装

如果推送不干净/被拒绝：

如果失败原因是非快进或同步问题，运行 pull 技能以合并 origin/main，解决冲突，并重新运行验证。
再次推送；仅当历史记录被重写时才使用 --force-with-lease。
如果失败是由于已配置的远程仓库的认证、权限或工作流限制导致的，则停止并显示确切的错误信息，而不是通过重写远程仓库或切换协议作为变通方法。

明确使用 .github/pull_request_template.md 编写/更新 PR 正文：

为本次变更的每个部分填写具体内容。
替换所有占位符注释（）。
保留模板中预期的项目符号/复选框。
如果 PR 已存在，刷新正文内容，使其反映 PR 的总体范围（分支上所有预期的工作），而不仅仅是最近的提交，包括新增的工作、移除的工作或变更的方法。
不要重用早期迭代中过时的描述文本。

# 识别分支
branch=$(git branch --show-current)

# 最小验证门
make -C elixir all

# 初始推送：尊重当前的 origin 远程仓库。
git push -u origin HEAD

# 如果因为远程仓库已更新而失败，使用 pull 技能。在
# pull 技能解决冲突并重新验证后，重试正常推送：
git push -u origin HEAD

# 如果已配置的远程仓库因认证、权限或工作流
# 限制而拒绝推送，停止并显示确切的错误信息。

# 仅当本地历史记录被重写时：
git push --force-with-lease origin HEAD

# 确保存在一个 PR（仅在缺失时创建）
pr_state=$(gh pr view --json state -q .state 2>/dev/null || true)
if [ "$pr_state" = "MERGED" ] || [ "$pr_state" = "CLOSED" ]; then
  echo "当前分支关联的 PR 已关闭；请创建新分支 + PR。" >&2
  exit 1
fi

# 编写一个清晰、易于理解的标题，总结已提交的变更。
pr_title="<为此变更编写的清晰 PR 标题>"
if [ -z "$pr_state" ]; then
  gh pr create --title "$pr_title"
else
  # 每次分支更新时重新考虑标题；如果范围发生变化，则进行编辑。
  gh pr edit --title "$pr_title"
fi

# 在验证前，编写/编辑 PR 正文以匹配 .github/pull_request_template.md。
# 示例工作流：
# 1) 打开模板并为此 PR 起草正文内容
# 2) gh pr edit --body-file /tmp/pr_body.md
# 3) 对于分支更新，重新检查标题/正文是否仍与当前差异匹配

tmp_pr_body=$(mktemp)
gh pr view --json body -q .body > "$tmp_pr_body"
(cd elixir && mix pr_body.check --file "$tmp_pr_body")
rm -f "$tmp_pr_body"

# 显示 PR URL 用于回复
gh pr view --json url -q .url

不要使用 --force；仅将 --force-with-lease 作为最后的手段。
区分同步问题与远程认证/权限问题：
- 对于非快进或分支过时问题，使用 pull 技能。
- 直接显示认证、权限或工作流限制错误，而不是更改远程仓库或协议。

🇺🇸English

Push

Prerequisites

gh CLI is installed and available in PATH.
gh auth status succeeds for GitHub operations in this repo.

Goals

Push current branch changes to origin safely.
Create a PR if none exists for the branch, otherwise update the existing PR.
Keep branch history clean when remote has moved.

Related Skills

pull: use this when push is rejected or sync is not clean (non-fast-forward, merge conflict risk, or stale branch).

Steps

Identify current branch and confirm remote state.
Run local validation (make -C elixir all) before pushing.
Push branch to origin with upstream tracking if needed, using whatever remote URL is already configured.
If push is not clean/rejected:
- If the failure is a non-fast-forward or sync problem, run the pull skill to merge origin/main, resolve conflicts, and rerun validation.
- Push again; use --force-with-lease only when history was rewritten.
- If the failure is due to auth, permissions, or workflow restrictions on the configured remote, stop and surface the exact error instead of rewriting remotes or switching protocols as a workaround.
Ensure a PR exists for the branch:
- If no PR exists, create one.
- If a PR exists and is open, update it.
- If branch is tied to a closed/merged PR, create a new branch + PR.
- Write a proper PR title that clearly describes the change outcome
- For branch updates, explicitly reconsider whether current PR title still matches the latest scope; update it if it no longer does.
Write/update PR body explicitly using .github/pull_request_template.md:
- Fill every section with concrete content for this change.
- Replace all placeholder comments ().
- Keep bullets/checkboxes where template expects them.
- If PR already exists, refresh body content so it reflects the total PR scope (all intended work on the branch), not just the newest commits, including newly added work, removed work, or changed approach.
- Do not reuse stale description text from earlier iterations.
Validate PR body with mix pr_body.check and fix all reported issues.
Reply with the PR URL from gh pr view.

Commands

# Identify branch
branch=$(git branch --show-current)

# Minimal validation gate
make -C elixir all

# Initial push: respect the current origin remote.
git push -u origin HEAD

# If that failed because the remote moved, use the pull skill. After
# pull-skill resolution and re-validation, retry the normal push:
git push -u origin HEAD

# If the configured remote rejects the push for auth, permissions, or workflow
# restrictions, stop and surface the exact error.

# Only if history was rewritten locally:
git push --force-with-lease origin HEAD

# Ensure a PR exists (create only if missing)
pr_state=$(gh pr view --json state -q .state 2>/dev/null || true)
if [ "$pr_state" = "MERGED" ] || [ "$pr_state" = "CLOSED" ]; then
  echo "Current branch is tied to a closed PR; create a new branch + PR." >&2
  exit 1
fi

# Write a clear, human-friendly title that summarizes the shipped change.
pr_title="<clear PR title written for this change>"
if [ -z "$pr_state" ]; then
  gh pr create --title "$pr_title"
else
  # Reconsider title on every branch update; edit if scope shifted.
  gh pr edit --title "$pr_title"
fi

# Write/edit PR body to match .github/pull_request_template.md before validation.
# Example workflow:
# 1) open the template and draft body content for this PR
# 2) gh pr edit --body-file /tmp/pr_body.md
# 3) for branch updates, re-check that title/body still match current diff

tmp_pr_body=$(mktemp)
gh pr view --json body -q .body > "$tmp_pr_body"
(cd elixir && mix pr_body.check --file "$tmp_pr_body")
rm -f "$tmp_pr_body"

# Show PR URL for the reply
gh pr view --json url -q .url

Notes

Do not use --force; only use --force-with-lease as the last resort.
Distinguish sync problems from remote auth/permission problems:
- Use the pull skill for non-fast-forward or stale-branch issues.
- Surface auth, permissions, or workflow restrictions directly instead of changing remotes or protocols.

Weekly Installs

132

Repository

odysseus0/symphony

GitHub Stars

First Seen

Mar 10, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

codex131

opencode11

gemini-cli11

claude-code11

github-copilot11

amp11