菜单
Use before telling the user a coding task is done or opening a PR. Run project verification commands, cite real exit codes, and block completion on missing evidence.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Keep coordinator and leaf context lean-batch reads, cap logs, use execute_code to filter-so swarms stay fast and within token limits.
Use at the start of non-trivial software tasks. Gather repo ground truth with batched reads and searches before planning or delegate_task.
Obey Plan 1A hook session phases so mutating tools, delegate_task sizing, and re-planning do not waste turns or trigger blocks.
Use when spawning delegate_task leaves for coding work. Pack self-contained goals and context so parallel Composer workers ship verifiable patches without coordinator chat history.
Require structured candidate-result JSON from swarm leaves so critique_candidates.py and synthesis run on evidence, not prose self-reports.
Enrich slim hook-injected delegate_tasks with touch map, failure excerpts, and verification commands so parallel leaves produce verifiable patches without coordinator chat history.
| name | heavy-ship-gate |
| description | Use before telling the user a coding task is done or opening a PR. Run project verification commands, cite real exit codes, and block completion on missing evidence. |
| version | 0.1.0 |
| author | CodeGraphTheory |
| license | MIT |
| metadata | {"hermes":{"tags":["heavy-coder","verification","tests","quality"],"related_skills":["heavy-team-default","heavy-synthesize-winner","test-driven-development","requesting-code-review"]}} |
Heavy Coder's SOUL contract requires scope, files, commands, tests, risks, and honest implementation status. This skill is the completion gate: no "done" without executed verification and reported results.
publish_pr.py --execute or any push the user requestedDo not use for:
verification_commands from team_coordinator.pyAGENTS.md / README / CONTRIBUTING in repo rootpackage.json, pyproject.toml, Makefile, scripts/ci_local.shterminal (foreground) for each required command; capture exit code and material stdout/stderr.ruff, mypy, eslint), run on touched paths or project default..env, tokens, or private keys in diffs.Done when: every required command has a recorded exit code and failures are fixed or explicitly reported as blockers.
When editing github.com/codegraphtheory/heavy-coder:
. .venv/bin/activate
./scripts/ci_local.sh
Includes validate_distribution.py, pytest, ruff, mypy, skin markup validator.
Release-relevant edits also need distribution.yaml version bump + CHANGELOG.md heading (see docs/coding-standards.md).
| Signal in repo | Default verify |
|---|---|
pyproject.toml + pytest | pytest -q |
package.json with test script | npm test |
go.mod | go test ./... |
Cargo.toml | cargo test |
scripts/ci_local.sh | run it |
Scope: <one line>
Files: <paths>
Commands:
- <cmd> -> exit <n>
Tests: <pass/fail summary from real output>
Risks: <residual>
Status: implemented | scaffolded | blocked
--ignore.Leaf summaries are self-reports. Ship gate commands run on the coordinator tree after synthesis, even if a leaf claimed green CI.
test-driven-development - when adding behavior, prefer RED-GREEN-REFACTOR before ship gate.requesting-code-review - optional deeper review before merge; ship gate is minimum bar.