New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Promoting Dev To Main

by Human-Agent-Society in Human-Agent-Society/CORAL

A skill your agent uses when preparing, reviewing, resolving conflicts for, or merging a CORAL release pull request from the long-lived dev branch into main.

Apache-2.0Auto-check passedDevelopment

Install Promoting Dev To Main

skills CLI
$ npx skills add Human-Agent-Society/CORAL --skill promoting-dev-to-main -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Human-Agent-Society/CORAL promoting-dev-to-main --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Human-Agent-Society/CORAL.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/promoting-dev-to-main .claude/skills/promoting-dev-to-main && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
promoting-dev-to-main
GitHub stars
1.1k
Token cost
~588 tokens
SKILL.md length
286 words
Files
2
Skills in repo
7
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when preparing, reviewing, resolving conflicts for, or merging a CORAL release pull request from the long-lived dev branch into main.

  • Works in 6 steps: Confirm the PR is exactly base=main,… → Review main..dev, required CI, and… → In GitHub, open the merge-method… → …
  • Resolving conflicts for
  • SKILL.md covers Core rule, Workflow, If GitHub reports conflicts and Red flags, plus 1 more section
  • Calls git and gh

What it does

Promoting Dev To Main is an agent skill from Human-Agent-Society/CORAL. Use when preparing, reviewing, resolving conflicts for, or merging a CORAL release pull request from the long-lived dev branch into main.

Its SKILL.md is about 590 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development, covering Pull requests. It works with GitHub. The repository describes itself as: Open-source autoresearch powered by autonomous coding agents. Run Claude Code, OpenCode, and Codex with grading, shared knowledge, and multi-agent evolution. Accepted at COLM 2026. The licence is Apache-2.0.

When your agent uses it

  • Resolving conflicts for
  • Merging a CORAL release pull request from the long-lived dev branch into main

Example prompts

  • “/promoting-dev-to-main”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Confirm the PR is exactly base=main, head=dev and no duplicate release
  2. Review main..dev, required CI, and deployment checks.
  3. In GitHub, open the merge-method dropdown and choose **Create a merge
  4. Keep the long-lived dev branch. Do not delete or force-push it.
  5. Fetch both branches and verify the released dev tip is an ancestor of
  6. Confirm post-merge CI, release automation, deployments, and production

What it can do on your machine

Read from SKILL.md and the folder at commit 0123dfb. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Promoting Dev To Main loads about 588 tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 286 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~40
When it runs · the whole SKILL.md, loaded when a task matches
~588

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Human-Agent-Society/CORAL at commit 0123dfb, republished under its Apache-2.0 licence (© Human-Agent-Society). 286 words, ~588 tokens.

Download SKILL.mdSave it as .claude/skills/promoting-dev-to-main/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
promoting-dev-to-main
description
Use when preparing, reviewing, resolving conflicts for, or merging a CORAL release pull request from the long-lived dev branch into main.

Promoting dev to main

Core rule

Merge dev → main release PRs with a merge commit. Never squash or rebase these promotions.

Ordinary contribution PRs still target dev and may be squash-merged. The release promotion is the exception because main must retain dev in its ancestry. Squashing a promotion makes the next release re-present old commits and can create large false conflicts.

Workflow

  1. Confirm the PR is exactly base=main, head=dev and no duplicate release PR is open.

  2. Review main..dev, required CI, and deployment checks.

  3. In GitHub, open the merge-method dropdown and choose Create a merge commit. With the CLI, use:

    bash
    gh pr merge <number> --repo Human-Agent-Society/CORAL --merge

  4. Keep the long-lived dev branch. Do not delete or force-push it.

  5. Fetch both branches and verify the released dev tip is an ancestor of main:

    bash
    git fetch origin dev main
git merge-base --is-ancestor origin/dev origin/main

    Exit status 0 is required.

  6. Confirm post-merge CI, release automation, deployments, and production smoke checks.

If GitHub reports conflicts

Do not force-rebase the shared dev branch. First inspect the topology and reproduce conflicts with git merge-tree.

If an earlier release was squash-merged, main may have the same tree as an earlier dev commit without sharing its ancestry. Verify tree equivalence before choosing a repair. Prefer merging main back into dev and pushing normally; use an ancestry-only ours merge only when exact tree equality proves main contains no unique content to preserve.

Red flags

  • GitHub's primary button says Squash and merge.
  • A command uses --squash, --rebase, or a force-push.
  • The release workflow proposes deleting dev.
  • Conflict resolution starts before checking commit topology and tree equality.

Stop when any red flag appears and return to the workflow above.

Quick reference

PRAllowed merge method
Feature/fix/docs branch → devRepository default; usually squash
dev → main release promotionMerge commit only

© Human-Agent-Society, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .claude/skills/promoting-dev-to-main of Human-Agent-Society/CORAL.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 0123dfb

Compare with similar skills

Promoting Dev To Main next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Promoting Dev To Main compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Promoting Dev To Main this skillHuman-Agent-Society/CORAL1.1k—~588Automated safety check: PassApache-2.0
GitHub Review Iterationprisma/orm48k—~2.2kAutomated safety check: PassApache-2.0
Cherry Studio PR ReviewCherryHQ/cherry-studio53k—~3.9kAutomated safety check: PassAGPL-3.0
Qiaomu Meta Skilljoeseesun/qiaomu-meta-skill383—~2.8kAutomated safety check: PassMIT
PR Cyclejaemk/cached2.1k—~4.8kAutomated safety check: NotesMIT
PR Reviewjaemk/self_update961—~1.5kAutomated safety check: NotesMIT

Similar skills

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Cherry Studio PR Review

    CherryHQ/cherry-studio

    Reviews Cherry Studio branches, pull requests, commits, files and docs against the project's own architecture, naming, API-boundary and UI rules, report-only by default.

    53k GitHub stars~3.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Qiaomu Meta Skill

    joeseesun/qiaomu-meta-skill

    Research, create, improve, migrate, evaluate, package, install-check, govern, and safely publish qiaomu-flavored agent skills from workflows, prompts, transcripts, docs, SOPs, runbooks, scripts, or…

    383 GitHub stars~2.8k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

  • PR Cycle

    jaemk/cached

    PR review-and-update cycle — the orchestrator that takes a PR from review to resolved.

    2.1k GitHub stars~4.8k tokensUpdated 9 days ago
    DevelopmentAuto-check: notes

  • PR Review

    jaemk/self_update

    Targeted, read-only review of a PR or checked-out branch. An agent skill from jaemk/self_update.

    961 GitHub stars~1.5k tokensUpdated 1 mo ago
    DevelopmentAuto-check: notes

  • Firewood Review

    ava-labs/firewood

    A skill your agent uses when reviewing ava-labs/firewood code changes — pull request or local workspace.

    153 GitHub stars~2.1k tokensUpdated yesterday
    DevelopmentAuto-check: notes

More from Human-Agent-Society/CORAL

  • Creating A Coral Task

    Human-Agent-Society/CORAL

    Author a new CORAL task — the three pieces that must line up (task.yaml, seed/, a packaged grader/), the coral init → coral validate → smoke-test loop, and how to pick a grader pattern (stdout…

    1.1k GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check passed

  • Running Coral Experiments

    Human-Agent-Society/CORAL

    Run and manage CORAL experiments from the operator side — launch agents with coral start (dotlist overrides, model/count, tmux vs local), monitor with coral status / coral log / coral show / the web…

    1.1k GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed

  • Coral Debug

    Human-Agent-Society/CORAL

    Verify and debug changes to CORAL itself — smallest reproduce loop per area (grader / daemon / CLI / hooks / manager / workspace / hub / template / config / web), where to look when something breaks…

    1.1k GitHub stars~1.8k tokensUpdated 1 mo ago
    Auto-check passed

  • Coral New Task

    Human-Agent-Society/CORAL

    End-to-end recipe for adding a new task under examples/ — the three pieces that have to line up (task.yaml, seed/, and grader/), what to put in each, the TaskGrader API surface, the coral validate →…

    1.1k GitHub stars~3.4k tokensUpdated 1 mo ago
    Auto-check passed

  • Setting Up Coral

    Human-Agent-Society/CORAL

    One-time machine setup after installing the coral CLI — register local agent runtimes as named bindings with coral setup / coral setup agent, validate them with coral agents doctor (incl.

    1.1k GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check passed

  • Coral Extend

    Human-Agent-Society/CORAL

    Add a new component to the CORAL framework itself — a new agent runtime under coral/agent/builtin/ (claudecode/codex/cursoragent style), a new CLI command in coral/cli/, a new bundled skill or…

    1.1k GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Promoting Dev To Main

What does Promoting Dev To Main do?

A skill your agent uses when preparing, reviewing, resolving conflicts for, or merging a CORAL release pull request from the long-lived dev branch into main. Promoting Dev To Main is an agent skill from Human-Agent-Society/CORAL. Use when preparing, reviewing, resolving conflicts for, or merging a CORAL release pull request from the long-lived dev branch into main.

When should I use Promoting Dev To Main?

Promoting Dev To Main fits situations like: resolving conflicts for; merging a CORAL release pull request from the long-lived dev branch into main.

How do I install Promoting Dev To Main in Claude Code?

Run `npx skills add Human-Agent-Society/CORAL --skill promoting-dev-to-main -a claude-code`. Or copy the skill folder (.claude/skills/promoting-dev-to-main in Human-Agent-Society/CORAL) into .claude/skills/promoting-dev-to-main in your project. Claude Code loads it when a task matches its description.

How do I install Promoting Dev To Main in Codex?

Run `npx skills add Human-Agent-Society/CORAL --skill promoting-dev-to-main -a codex`. Or copy the skill folder (.claude/skills/promoting-dev-to-main in Human-Agent-Society/CORAL) into .agents/skills/promoting-dev-to-main in your project. Codex loads it when a task matches its description.

Can I use Promoting Dev To Main in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Human-Agent-Society/CORAL --skill promoting-dev-to-main -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/promoting-dev-to-main, .gemini/skills/promoting-dev-to-main, .github/skills/promoting-dev-to-main and .opencode/skills/promoting-dev-to-main in your project.

What does Promoting Dev To Main need to run?

Going by SKILL.md and its folder, Promoting Dev To Main needs the command-line tools its instructions call (git and gh).

Does Promoting Dev To Main access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Promoting Dev To Main safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Promoting Dev To Main use?

Promoting Dev To Main is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Promoting Dev To Main use?

About 588 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Promoting Dev To Main?

Skills that share tags, products or a category with Promoting Dev To Main: GitHub Review Iteration (prisma/orm, 48k stars), Cherry Studio PR Review (CherryHQ/cherry-studio, 53k stars), Qiaomu Meta Skill (joeseesun/qiaomu-meta-skill, 383 stars) and PR Cycle (jaemk/cached, 2.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Promoting Dev To Main?

Human-Agent-Society (a GitHub organization) maintains it in Human-Agent-Society/CORAL, which has 1,060 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 8, 2026.

Source: Human-Agent-Society/CORAL on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.