agentleFS
CarriedWorldUniverseCarriedWorldUniverse/nexus/.agents/skills/merge/SKILL.md

merge

Skill0 starsChanged 36 days agoApache-2.0View on GitHub

How to land a reviewed PR on nexus — CI green including security scans, squash and delete, never force.

58 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use addskill, apply-firmware and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ryanportfolioSkill

    addskill

    Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

    Also in 6 projects that use this

  • ryanportfolioSkill

    apply-firmware

    Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.

    Also in 6 projects that use this

  • +10 more from ryanportfolio

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 52 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Don't merge until it's actually done and green.

    line 9
  2. Distinctive:

    Wait for CI to be green on all legs — including the security scans (load the security skill if unsure what must pass).

    line 13
  3. Distinctive:

    If a leg fails on a known flake (e.g.

    line 14
  4. Distinctive:

    If a leg fails for a real reason, it's not ready.

    line 15
  5. Very specific:

    NEVER use --admin to bypass required checks.

    line 20
  6. Distinctive:

    After merge, the work isn't live yet — load the release skill to deploy and verify.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 52 edited versions of this file we could read. “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

merge

Don't merge until it's actually done and green. A PR that "should pass" is not ready.

Steps

  1. Confirm the PR is reviewed and the work is complete.
  2. Wait for CI to be green on all legs — including the security scans (load the security skill if unsure what must pass).
  3. If a leg fails on a known flake (e.g. a timing test), re-run that leg. Read the failure first to be sure it's a flake, not a real break — don't re-run blind.
  4. If a leg fails for a real reason, it's not ready. Fix it; don't merge around it.
  5. Merge with squash and delete the branch.
  6. Summarise back what landed.

Rules

  • NEVER use --admin to bypass required checks. Green means green.
  • Merge authority is the operator's standing pre-authorization to merge after review. Pause for destructive or cross-cutting changes.
  • After merge, the work isn't live yet — load the release skill to deploy and verify.

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.