Menu
Execute git operations for PR-based releases (commit, push, and enforce the post-merge automation PR title)
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Creates a test playbook for a task — `task.test-create [id]`, `test.create [id]`, or any request to generate an E2E test runbook from a task file. Produces a complete, executable playbook under `.smaqit/user-testing/tests/` with build-gate, deploy-gate, and live-service E2E validation where the task touches live services.
End session by documenting the entire conversation. Use at session completion to create history entries.
Bootstrap or refresh a smaqit project by inferentially synchronizing Codex, Claude Code, and GitHub Copilot project instructions around a canonical root AGENTS.md, then creating the base project directories (docs/, assets/, assets/raw/). Use when the user asks to start, initialize, reinitialize, or refresh a smaqit project.
Execute git operations (commit, tag, push) for local releases
Produces a structured parity assessment comparing any two software systems — frameworks, libraries, platforms, or products. Identifies the current project from session context, studies the target system, checks domain compatibility, then outputs validated Mermaid diagrams and a written ASSESSMENT.md. Trigger phrase: `parity.assess <name>`.
Manages a live Q&A knowledge manifest at `.smaqit/compendium.md`. Invoked when the user says `list compendium`, `fetch from compendium [query]`, `update compendium [question]`, or `remove from compendium [question]`. Lists all Q&A entries grouped by category, semantically searches for relevant entries, upserts a Q&A pair (add or update), or removes an entry after confirmation.
Baseado na classificação ocupacional SOC
| name | smaqit.release-git-pr |
| description | Execute git operations for PR-based releases (commit, push, and enforce the post-merge automation PR title) |
| metadata | {"version":"0.3.0"} |
Execute git operations required for PR-based releases: stage changes, commit to PR branch, and push via git push directly (using the current environment's git/gh credentials).
Use this skill for PR-based releases (running in CI/CD or agent workflow) after all files have been prepared. This skill:
git push directly (using the current environment's git/gh credentials)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
Push the commit directly to the PR branch:
git push origin <branch-name>
Do NOT:
main directly — this workflow is PR-basedCRITICAL: This step is not optional. A wrong PR title causes the post-merge release workflow to skip all jobs silently.
Check the current PR title:
gh pr view --json title -q .title
The PR title MUST match one of these patterns:
Prepare release vX.Y.ZRelease vX.Y.ZIf the title does NOT match, update it immediately:
gh pr edit --title "Prepare release vX.Y.Z"
Common failure patterns to watch for:
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 |
git push fails | Network issue, auth failure, or diverged branch | Check git status/gh auth status, resolve, 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 | git push directly (using the current environment's git/gh credentials) |
| Git credentials | User's local credentials | User's local/agent git credentials |
| When to use | Developer's local machine | CI/CD or agent workflow |
git push directly (using the current environment's git/gh credentials).github/workflows/post-merge-release.yml for workflow details