메뉴
Use when preparing, reviewing, resolving conflicts for, or merging a CORAL release pull request from the long-lived dev branch into main.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SOC 직업 분류 기준
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/Human-Agent-Society/CORAL --skill promoting-dev-to-main명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
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` → smoke-test loop, and the common mistakes (repo_path pointing at the wrong dir, score direction backwards, hidden answer keys leaking into seed/, grader writing to codebase_path which the daemon force-removes, private-vs-public confusion, missing `run()` signature). Use whenever the user wants to add a new CORAL task or port an existing benchmark into 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 float, test pass-rate, ratio-vs-baseline, multi-metric, or an LLM rubric judge). Use whenever the user wants to create a CORAL task, write or wire a grader, port a benchmark into CORAL, score open-ended outputs (reports/memos) with a judge, or debug a grader that crashes on the seed / ranks the leaderboard backwards / leaks the answer key. Deep references for the TaskGrader API, grader patterns, rubric judges, and the full task.yaml schema live alongside this skill.
Autonomously create, test, and optimize skills by detecting reusable patterns in your own work. Use when you notice repeated tool sequences, recurring code patterns across attempts, or insights that should be captured as a packaged skill. Also use to benchmark and iterate on existing skills.
| 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. |
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.
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.
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.
--squash, --rebase, or a force-push.dev.Stop when any red flag appears and return to the workflow above.
| PR | Allowed merge method |
|---|---|
Feature/fix/docs branch → dev | Repository default; usually squash |
dev → main release promotion | Merge commit only |