Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Promoting dev to main · human-agent-society | DecimalAI

code reviewby human-agent-society

Promoting dev to main

human-agent-society/promoting-dev-to-main

Source human-agent-society/coral ↗License Apache-2.0

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

SkillScore91Maintained

Automatic

DevOps & SRE pack

Last verified 8/16/2026

What it changes

Passed 18 of 20 test cases with the skill, and 14 of 20 without it.

Without skill68%

With skill91%

Checks it passed that the model alone missed

Specifies reviewing main..dev range.
Verifies no duplicate release PR is currently open.
Runs git merge-base --is-ancestor to verify ancestry.

and 4 more in the full report

5 fixed15 passed either way2 still failing0 broke

Pass-rate lift: +23 pp
Tokens: -21%
Agent turns: 0%
Response time: -60%

Model gemini-3.6-flashMeasured 8/16/2026v120 of 22 cases passed with skill · 20 comparable

Tokens, turns and time describe resource use, not a dollar price.

Use this skill

Save it into your project's skills folder. Claude Code picks it up in its next session.

curl -fsSL --create-dirs -o .claude/skills/human-agent-society-promoting-dev-to-main/SKILL.md https://app.decimal.ai/s/human-agent-society-promoting-dev-to-main/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add human-agent-society-promoting-dev-to-main, and start Claude Code with claude --plugin-dir "$(git rev-parse --show-toplevel)/.agents"

1 · One-time — install the CLI (docs ↗)

pip install "decimalai>=0.15"

2 · Get the skill — writes .agents/skills/human-agent-society-promoting-dev-to-main/ and pins it in .decimal/skills.lock

decimalai skills add human-agent-society-promoting-dev-to-main

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/human-agent-society-promoting-dev-to-main/SKILL.md https://app.decimal.ai/s/human-agent-society-promoting-dev-to-main/SKILL.md

Raw file: /s/human-agent-society-promoting-dev-to-main/SKILL.md ↗ · machine-readable summary at /s/human-agent-society-promoting-dev-to-main.json ↗

Safety checks: 3 of 3 passed

Code scan CleanIntent PassedContent Clean

See it in action

One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.

1 of 5

Prompt

PR #508 is ready for our release promotion from `dev` to `main` in the CORAL project. Can you perform the merge using the GitHub CLI, make sure the `dev` branch isn't deleted, and execute the Git history verification check to confirm the relationship between the branches?

What was checked, without and with the skill
Checked	Without skill	With skill
Includes the explicit repository flag --repo Human-Agent-Society/CORAL in the CLI command.	Missed	Passed
Instructs to preserve the dev branch without deleting it post-merge.	Missed	Passed
Runs git merge-base --is-ancestor to verify ancestry.	Missed	Passed

case-02 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted

What's inside

The instructions your model reads when the skill loads.

SKILL.md63 linessingle file

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

Confirm the PR is exactly base=main, head=dev and no duplicate release PR is open.
Review main..dev, required CI, and deployment checks.
In GitHub, open the merge-method dropdown and choose Create a merge commit. With the CLI, use:
```
gh pr merge <number> --repo Human-Agent-Society/CORAL --merge
```
Keep the long-lived dev branch. Do not delete or force-push it.
Fetch both branches and verify the released dev tip is an ancestor of main:
```
git fetch origin dev main
git merge-base --is-ancestor origin/dev origin/main
```
Exit status 0 is required.
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

Track record

Benchmark

18 / 20

test cases passed, vs 14 / 20 without

Adoption

Users: 0
Times used: 0

Safety and source details

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026

View 15 scanner checks

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

human-agent-society / coral

.claude/skills/promoting-dev-to-main/SKILL.md

View on GitHub ↗

License Apache-2.0Imported 8/3/2026Version v1

More skills from the same source and nearby in the registry, with their headline benchmark lift.

Ready to supercharge your AI agents?

See it in action

What's inside

Promoting dev to main

Core rule

Workflow

If GitHub reports conflicts

Track record

Benchmark

Adoption

SkillSafety

Source

Related skills