菜单
Execute git operations for PR-based releases (commit, push via report_progress)
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Collect changes, assess severity, and suggest next version for a release
Validate git state and prepare all files (CHANGELOG.md, version files) for release
End session by documenting the entire conversation. Use at session completion to create history entries.
Start a new chat with full project context. Use when beginning a session to load README, recent history, and task planning.
Generate a succinct title for the current session based on work accomplished. Use when finishing sessions to create history file titles.
Mark a task as completed with verification. Use when finishing tasks to update status and verify criteria.
| name | smaqit.release-git-pr |
| description | Execute git operations for PR-based releases (commit, push via report_progress) |
| metadata | {"version":"0.2.0"} |
Execute git operations required for PR-based releases: stage changes, commit to PR branch, and push via report_progress tool.
Use this skill for PR-based releases (running in CI/CD or agent workflow) after all files have been prepared. This skill:
report_progress tool (handles credentials internally)Do NOT use this skill for local releases - use release-git-local instead.
Stage CHANGELOG.md and any confirmed version files:
git add CHANGELOG.md
If version files were updated:
git add package.json pyproject.toml
Verify staged changes:
git --no-pager diff --cached --name-only
Create commit with release preparation message:
git commit -m "Prepare release vX.Y.Z"
Use "Prepare release" not "Release" because the actual release happens after PR merge to main.
Verify commit was created:
git --no-pager log -1 --oneline
Use the report_progress tool to push changes to the PR branch:
This tool:
git pushDo NOT:
git push directly (credentials not available in agent environment)CRITICAL: Ensure the PR title matches the pattern required for post-merge automation.
The PR title must follow one of these formats:
Prepare release vX.Y.ZRelease vX.Y.Z(Both case-insensitive variants are supported)
Post-merge workflow automatically:
vX.Y.ZNo manual intervention required!
Document in PR description:
## Post-Merge Automation
When this PR is merged to `main`, the post-merge workflow will automatically:
✅ Create git tag `vX.Y.Z`
✅ Build binaries for Linux, macOS, Windows (amd64/arm64)
✅ Publish GitHub Release with binaries and changelog
Workflow: `.github/workflows/post-merge-release.yml`
Provide a summary of PR operations:
success: true
commit_sha: abc123def456
pr_updated: true
pr_branch: feature/release-v0.3.0
pr_title: "Prepare release vX.Y.Z"
post_merge_automation: true
Output fields:
success: Boolean indicating all operations completedcommit_sha: SHA of the release preparation commitpr_updated: Boolean indicating PR was updated successfullypr_branch: The feature branch containing release changespr_title: The PR title that triggers post-merge automationpost_merge_automation: Boolean indicating workflow will handle release| Error | Likely Cause | Suggested Action |
|---|---|---|
nothing to commit | Files unchanged or not staged | Verify changes were made and staged correctly |
report_progress fails | PR update failed | Check PR status and retry |
| Already on main branch | Wrong workflow used | Use release-git-local skill for local releases |
| Aspect | release-git-local | release-git-pr |
|---|---|---|
| Branch | main | Feature/PR branch |
| Commit message | "Release vX.Y.Z" | "Prepare release vX.Y.Z" |
| Tag creation | ✅ Yes, immediately | ❌ No, after merge to main |
| Push method | git push directly | report_progress tool |
| Git credentials | User's local credentials | Handled by report_progress |
| When to use | Developer's local machine | CI/CD or agent workflow |
report_progress tool handles authentication - no need for credential setup.github/workflows/post-merge-release.yml for workflow details