github-pr-acceptance
/github-pr-acceptance
Use when the user explicitly asks to accept or merge a GitHub pull request and the PR must show as merged on GitHub, not only in local git history.
- Author
- friuns2 ↗
- Repository
- codex-mobile ↗
- Licence
- MIT
- Last repository change
- 20.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 20.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when the user explicitly asks to accept or merge a GitHub pull request and the PR must show as merged on GitHub, not only in local git history.
Original author description
Use when the user explicitly asks to accept or merge a GitHub pull request and the PR must show as merged on GitHub, not only in local git history.
How it works
- When To Use
- Goal
- Workflow
- Notes
SKILL.md preview
---
name: github-pr-acceptance
description: Use when the user explicitly asks to accept or merge a GitHub pull request and the PR must show as merged on GitHub, not only in local git history.
---
# GitHub PR Acceptance
## When To Use
Use this skill when the user explicitly asks to accept/merge a pull request on GitHub (not just locally).
## Goal
Ensure the PR is shown as **MERGED** on GitHub, with `mergedAt` and `mergeCommit` populated.
## Workflow
1. Perform local integration first
- Merge intended work into local `main` using repository merge rules.
2. Push `main` to canonical remote
- For this project, canonical remote is `https://github.com/friuns2/codexUI.git`.
3. Verify PR state
- Run:
- `gh pr view <number> --repo friuns2/codexUI --json state,mergedAt,mergeCommit,mergeStateStatus,url`
- If `state` is `MERGED`, stop.
4. If still `OPEN`
- If `mergeStateStatus` is `DIRTY` (common after rebase or cross-repo PR):
- push reconciled branch to PR head ref.
- if still open, create a no-content linkage merge commit on `main` against exact PR head SHA:
- `git checkout main`
- `git merge --no-ff -s ours <pr-head-sha> -m "Merge pull request #<number> from <owner>/<branch>"`
- push `main` again.
5. Final verification (mandatory)
- Re-run `gh pr view ...` and confirm:
- `state: MERGED`
- `mergedAt` is non-null
- `mergeCommit` is non-null
## Notes
- Local merge alone is not enough when user asks for GitHub acceptance.
- Cross-repo PRs may remain open even after equivalent code lands if ancestry/linkage is missing.
- If contributor attribution matters, avoid rewriting PR commit ancestry where possible.
Versions
The database has no other skills named github-pr-acceptance.
Database snapshot: 13.11.2026 · package version 8c85a9cec2be (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 86merge-github-pr
Use when safely merge GitHub pull requests that are ready - 90merge-pull-request
Use when merging a single GitHub pull request. Handles pre-flight checks, waits for CI, and executes the merge with the repo's default method or merge queue. - 100yeet
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`). - 100merge-pr
Safely merges GitHub pull requests using gh CLI. Use when the user wants to merge a PR, merge a pull request, or complete code review. - 100pr-land
Use when asked to merge or land a pull request ("merge it", "land it", "ship it", "merge when clean"), or to clean up the worktree and branch of a PR that is already merged. - 91github-pr-audit
Use when auditing a GitHub PR or issue before merge.