agentleFS
Sign inStart free
friuns2friuns2/codexUI/.agents/skills/github-pr-acceptance/SKILL.md

github-pr-acceptance

Skill956 starsChanged 3 months agoMITView on GitHub

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.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. friuns2/codex-mobile★ 931100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user explicitly asks to accept/merge a pull request on GitHub (not just locally).

    line 10
  2. Very specific:

    Ensure the PR is shown as MERGED on GitHub, with mergedAt and mergeCommit populated.

    line 14
  3. Very specific:

    If state is MERGED, stop.

    line 27
  4. Very specific:

    If mergeStateStatus is DIRTY (common after rebase or cross-repo PR):

    line 30
  5. Distinctive:

    if still open, create a no-content linkage merge commit on main against exact PR head SHA:

    line 32
  6. Distinctive:

    If contributor attribution matters, avoid rewriting PR commit ancestry where possible.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.
  1. Push main to canonical remote
  • For this project, canonical remote is https://github.com/friuns2/codexUI.git.
  1. Verify PR state
  • Run:
    • gh pr view <number> --repo friuns2/codexUI --json state,mergedAt,mergeCommit,mergeStateStatus,url
  • If state is MERGED, stop.
  1. 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.
  1. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free