agentleFS
dedalus-labsdedalus-labs/wingman/.agents/skills/promote/SKILL.md

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

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.
  • NVIDIASkill

    research

    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

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
  1. Distinctive:

    Default: promote current branch → main

    line 14
  2. Distinctive:

    If no commits, report that target is up to date and stop

    line 39
  3. Very specific:

    If --dry-run, print the body and stop

    line 45
  4. Very specific:

    Create the PR via gh pr create --base <to> --head <from> --title "chore(release): promote <from> → <to>" --body "..."

    line 46

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

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

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-run prints the PR body without creating it
  • Commits are grouped by conventional commit type into changelog sections

Changelog Sections

PrefixSection
featFeatures
fixBug Fixes
refactorRefactors
perfPerformance
testTests
docsDocumentation
chore, ciChores

Unrecognized prefixes go under Chores.

Task

  1. Parse $ARGUMENTS for --from, --to, --dry-run
  2. Fetch the latest from origin for both branches
  3. Get the commit list: git log --format="%H %s" origin/<to>..origin/<from>
  4. If no commits, report that target is up to date and stop
  5. 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
  6. If --dry-run, print the body and stop
  7. Create the PR via gh pr create --base <to> --head <from> --title "chore(release): promote <from> → <to>" --body "..."
  8. Return the PR URL

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.