promote
Skill181 starsChanged 7 months agoMITView on GitHub
Create a changelog-style promotion PR between two branches. Use for release promotions or branch-to-branch merges with a structured changelog.
- Commits and pushes
19 other projects use a version of this.
Adopted by
Most recently taken up by
- warrendeanlangeveldt/code-kittheir own version, first seen Nov 15, 2026
- HiteSit/real-scientist-skillstheir own version, first seen Nov 15, 2026
- anotherben/claude-harnesstheir own version, first seen Nov 8, 2026
- ArcticFox2029/chamnantheir own version, first seen Nov 5, 2026
- jbaruch/nanoclaw-hosttheir own version, first seen Oct 31, 2026
- anis-dr/skillstheir own version, first seen Oct 15, 2026
Used with
Projects with it also use research.
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.
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 3 projects that use this
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- oliver-kriska/claude-elixir-phoenix★ 573same name
- HiteSit/real-scientist-skills★ 27same name
- wrg32786/aigent-os★ 26same name
- Hassaan146/claude-skills★ 18same name
- shahshrey/unclaw★ 17same name
- ArcticFox2029/chamnan★ 10same name
- nmhjklnm/yaohe★ 9same name
- anotherben/claude-harness★ 7same name
- anis-dr/skills★ 4same name
- Hussain-Elfalah/Agentic-Skills★ 2same name
9 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.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Default: promote current branch → main
- Distinctive: line 39
If no commits, report that target is up to date and stop
- Very specific: line 45
If --dry-run, print the body and stop
- Very specific: line 46
Create the PR via gh pr create --base <to> --head <from> --title "chore(release): promote <from> → <to>" --body "..."
“Common” is measured: kept by at least 6 in 10 of the 16 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
Context (auto-detected)
- Commits to promote: !
git log --oneline origin/main..HEAD 2>/dev/null || echo "(no commits ahead of main)"
Rules
- Default: promote current branch →
main --from <branch>overrides source (default: current branch)--to <branch>overrides target (default:main)--dry-runprints the PR body without creating it- Commits are grouped by conventional commit type into changelog sections
Changelog Sections
| Prefix | Section |
feat | Features |
fix | Bug Fixes |
refactor | Refactors |
perf | Performance |
test | Tests |
docs | Documentation |
chore, ci | Chores |
Unrecognized prefixes go under Chores.
Task
- Parse
$ARGUMENTSfor--from,--to,--dry-run - Fetch the latest from origin for both branches
- Get the commit list:
git log --format="%H %s" origin/<to>..origin/<from> - If no commits, report that target is up to date and stop
- Build the changelog body:
- Group commits by section using the table above
- Each bullet:
* **scope:** description ([short-hash](commit-url))or* description ([short-hash](commit-url))if unscoped - Include a "Full Changelog" comparison link
- Order sections: Features, Bug Fixes, Refactors, Performance, Tests, Documentation, Chores
- If
--dry-run, print the body and stop - Create the PR via
gh pr create --base <to> --head <from> --title "chore(release): promote <from> → <to>" --body "..." - Return the PR URL
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.

