agentleFS
ericmjlericmjl/skills/skills/github-auto-merge-setup/SKILL.md

github-auto-merge-setup

Skill42 starsChanged 50 days agoNo licenceView on GitHub

Diagnose and fix 'gh pr merge --auto' failures and set up CI-green auto-merge for GitHub repos/workflows. Use when: 'gh pr merge --auto' or a workflow merge step fails with an enablePullRequestAutoMerge error; auto-merge silently not working; enabling auto-merge for scheduled dependency-update workflows (dependabot etc.); adding a ruleset/branch protection with required status checks and choosing safe required checks; choosing merge flags (--rebase/--squash); a release workflow's push to main rejected with GH013 rule violations; a half-landed release (PyPI/tag published but main never got the 'Bump version' commit, or releases dying at the 'already on PyPI' guard); 'gh pr merge --admin' no-opping while the PR stays BLOCKED under a ruleset (admins are NOT exempt; only bypass_actors); or 'N of M required status checks are expected'. The three-layer gate stack and one-command diagnosis live in the body.

  • Reads credentials
  • Commits and pushes

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “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.

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.