coral-debug
Verify and debug changes to CORAL itself — smallest reproduce loop per area (grader / daemon / CLI / hooks / manager / workspace…
@human-agent-societyInstall SkillAutomation
Skill
/promoting-dev-to-main
Use when preparing, reviewing, resolving conflicts for, or merging a CORAL release pull request from the long-lived dev branch into main.
Claude Code
$ npx -y skills add Human-Agent-Society/CORAL --skill promoting-dev-to-main --agent claude-code
Codex
$ npx skills add Human-Agent-Society/CORAL --skill promoting-dev-to-main -a codex -y
Cursor
$ npx skills add Human-Agent-Society/CORAL --skill promoting-dev-to-main -a cursor -y
Gemini CLI
$ npx skills add Human-Agent-Society/CORAL --skill promoting-dev-to-main -a gemini-cli -y
GitHub Copilot
$ npx skills add Human-Agent-Society/CORAL --skill promoting-dev-to-main -a github-copilot -y
OpenCode
$ npx skills add Human-Agent-Society/CORAL --skill promoting-dev-to-main -a opencode -y
Windsurf
$ npx skills add Human-Agent-Society/CORAL --skill promoting-dev-to-main -a windsurf -y
SKILL.md
promoting-dev-to-main.SKILL.mdname: 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:
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`:
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
| PR | Allowed merge method | |---|---| | Feature/fix/docs branch → `dev` | Repository default; usually squash | | `dev` → `main` release promotion | Merge commit only |
Read more
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:
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`:
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
| PR | Allowed merge method | |---|---| | Feature/fix/docs branch → `dev` | Repository default; usually squash | | `dev` → `main` release promotion | Merge commit only |
Ships withcoral
Robust, lightweight infrastructure for multi-agent self-evolution, built for autoresearch. CORAL is infrastructure for autonomous AI agent organizations that run experiments, share knowledge, and continuously improve solutions.
1.1k12 skills4 agents
Stars on GitHub
Momentum
- stars in total
- 1.1k
Other skills on coral.
@human-agent-societyInstall Skillcoral-extend
Add a new component to the CORAL framework itself — a new agent runtime under `coral/agent/builtin/`…
@human-agent-societyInstall Skillcoral-new-task
End-to-end recipe for adding a new task under `examples/` — the three pieces that have to line up (`task.yaml`, `seed/`, and…
@human-agent-societyInstall Skillcreate-notes
Write a note to {shared_dir}/notes/ that future agents can actually act on. Use after every coral eval, when a heartbeat (reflect…
@human-agent-societyInstall Skilldeep-research
Research the problem domain before coding. Web search for techniques, save raw sources, write structured findings, update the…
@human-agent-societyInstall Skillorganize-files
Organize the shared notes directory when it becomes hard to navigate. Restructure within research/ and experiments/, deduplicate,…
@human-agent-societyInstall SkillMore skills from other plugins.
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers…
@browser-useInstall Skillagent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling…
@vercel-labs-2Install Skill
Questions about promoting-dev-to-main.
- Which coding agents can use promoting-dev-to-main?
- promoting-dev-to-main installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.