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
- onetimesecret/onetimesecrettheir own version, first seen Nov 16, 2026
- Kealman/cland-v0their own version, first seen Nov 15, 2026
- Trixx4191/asrartheir own version, first seen Nov 15, 2026
- automagik-si/genietheir own version, first seen Nov 15, 2026
- ryanportfolio/Corewise.Academytheir own version, first seen Nov 12, 2026
- ToolJet/ToolJettheir own version, first seen Nov 12, 2026
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.
ryanportfolioSkilladdskill
Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.
Also in 6 projects that use this
ryanportfolioSkillapply-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
Other versions58 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 58
- microsoft/vscode★ 195ksame name
- remotion-dev/remotion★ 73ksame name
- withastro/astro★ 64ksame name
- ToolJet/ToolJet★ 41ksame name
- Openpanel-dev/openpanel★ 7.3ksame name
- raine/workmux★ 3ksame name
- onetimesecret/onetimesecret★ 3ksame name
- jtenniswood/espcontrol★ 1.2ksame name
- K9i-0/ccpocket★ 1.1ksame name
- r1n7aro/Locus★ 759same name
48 more not listed
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 repository21 other files it gives its agents.
- browserbaseSkill
- cairnSkill
- developmentSkill
- dispatchSkill
- house-styleSkill
- kimi-subagentSkill
- lean-design-standardSkill
- nexus-authSkill
- nexus-jiraSkill
- orchestrateSkill
- orchestratorSkill
- planningSkill
- releaseSkill
- remote-opsSkill
- reviewSkill
- securitySkill
- specSkill
- ticket-pipelineSkill
- vision-reviewSkill
- workflow-basicsSkill
- writing-skillsSkill
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
- Distinctive: line 9
Don't merge until it's actually done and green.
- Distinctive: line 13
Wait for CI to be green on all legs — including the security scans (load the security skill if unsure what must pass).
- Distinctive: line 14
If a leg fails on a known flake (e.g.
- Distinctive: line 15
If a leg fails for a real reason, it's not ready.
- Very specific: line 20
NEVER use --admin to bypass required checks.
- Distinctive: line 22
After merge, the work isn't live yet — load the release skill to deploy and verify.
“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.
Files
merge
Don't merge until it's actually done and green. A PR that "should pass" is not ready.
Steps
- Confirm the PR is reviewed and the work is complete.
- Wait for CI to be green on all legs — including the security scans (load the security skill if unsure what must pass).
- 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.
- If a leg fails for a real reason, it's not ready. Fix it; don't merge around it.
- Merge with squash and delete the branch.
- Summarise back what landed.
Rules
- NEVER use
--adminto 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.
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
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.

