Run any Skill in Manus with one click

heavy-issue-to-merge

Stars21

Forks1

UpdatedJune 25, 2026 at 07:59

Coordinate Heavy Coder issue-to-PR and future fail-closed issue-to-merge workflows. Current phase provides contracts, dry-run scripts, and safety gates only.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

codegraphtheory

codegraphtheory/heavy-coder

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

19 files

SKILL.md

readonly

name	heavy-issue-to-merge
description	Coordinate Heavy Coder issue-to-PR and future fail-closed issue-to-merge workflows. Current phase provides contracts, dry-run scripts, and safety gates only.
version	0.1.0
author	CodeGraphTheory
license	MIT

Heavy Issue to Merge

Use this skill when a user asks Heavy Coder to implement a repository change, process a GitHub issue, open a pull request, repair CI, or consider unattended merge.

Current status

Scaffolded. Do not claim autonomous issue-to-merge is implemented.

Required workflow

Discover the current repository and verify prerequisites.
Triage the task and choose width 3 or 5 per heavy_coder.candidate_widths (default 3). Use single-agent mode only when the user explicitly requests it.
Keep candidate workers independent until critique.
For repository-changing candidates, use isolated git worktrees once worktree lifecycle is implemented.
Require structured candidate output matching schemas/candidate-result.schema.json.
Critique candidates against correctness, test evidence, regression risk, scope discipline, maintainability, and repository conventions.
Synthesize one final implementation.
Use a fresh verifier context for final inspection and tests.
For merge, require all fail-closed policy gates.

Helper scripts

Dangerous GitHub writes require explicit --execute (default is dry-run).

Script	Purpose
`doctor.py`	Environment and team-config checks (exit non-zero if python/git missing)
`repo_discovery.py`	Repository root, branch, remote, test heuristics
`worktrees.py`	`plan`, `list`, `create --execute`, `remove --execute` for candidate isolation
`validate_candidate.py`	JSON schema validation for candidate results
`claim_issue.py`	Issue claim labels/comments (`--execute` uses `gh`)
`publish_pr.py`	Open PR (`--execute` uses `gh pr create`)
`merge_pr.py`	Fail-closed stub (merge not implemented)
`policy_gate.py`	Deterministic merge-policy evaluation
`github_state.py`	Label projection helpers
`collect_evidence.py`	Local git evidence snapshot

Coordinator entrypoints at repo scripts/:

team_coordinator.py: emit delegate_task specs
critique_candidates.py: blind ranking of candidate JSON
heavy_coding_flow.py: doctor + plan + worktree plan in one step

References

Read the bundled references before implementation:

references/candidate-protocol.md
references/repair-protocol.md
references/security-policy.md

More from this repository

same repository

heavy-context-budget

codegraphtheory/heavy-coder

Keep coordinator and leaf context lean-batch reads, cap logs, use execute_code to filter-so swarms stay fast and within token limits.

2026-06-2521

heavy-explore-first

codegraphtheory/heavy-coder

Use at the start of non-trivial software tasks. Gather repo ground truth with batched reads and searches before planning or delegate_task.

2026-06-2521

heavy-hook-phases

codegraphtheory/heavy-coder

Obey Plan 1A hook session phases so mutating tools, delegate_task sizing, and re-planning do not waste turns or trigger blocks.

2026-06-2521

heavy-leaf-brief

codegraphtheory/heavy-coder

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.

2026-06-2521

heavy-leaf-candidate-output

codegraphtheory/heavy-coder

Require structured candidate-result JSON from swarm leaves so critique_candidates.py and synthesis run on evidence, not prose self-reports.

2026-06-2521

heavy-pre-dispatch-enrich

codegraphtheory/heavy-coder

Enrich slim hook-injected delegate_tasks with touch map, failure excerpts, and verification commands so parallel leaves produce verifiable patches without coordinator chat history.

2026-06-2521

name	heavy-issue-to-merge
description	Coordinate Heavy Coder issue-to-PR and future fail-closed issue-to-merge workflows. Current phase provides contracts, dry-run scripts, and safety gates only.
version	0.1.0
author	CodeGraphTheory
license	MIT

Heavy Issue to Merge

Use this skill when a user asks Heavy Coder to implement a repository change, process a GitHub issue, open a pull request, repair CI, or consider unattended merge.

Current status

Scaffolded. Do not claim autonomous issue-to-merge is implemented.

Required workflow

Discover the current repository and verify prerequisites.
Triage the task and choose width 3 or 5 per heavy_coder.candidate_widths (default 3). Use single-agent mode only when the user explicitly requests it.
Keep candidate workers independent until critique.
For repository-changing candidates, use isolated git worktrees once worktree lifecycle is implemented.
Require structured candidate output matching schemas/candidate-result.schema.json.
Critique candidates against correctness, test evidence, regression risk, scope discipline, maintainability, and repository conventions.
Synthesize one final implementation.
Use a fresh verifier context for final inspection and tests.
For merge, require all fail-closed policy gates.

Helper scripts

Dangerous GitHub writes require explicit --execute (default is dry-run).

Script	Purpose
`doctor.py`	Environment and team-config checks (exit non-zero if python/git missing)
`repo_discovery.py`	Repository root, branch, remote, test heuristics
`worktrees.py`	`plan`, `list`, `create --execute`, `remove --execute` for candidate isolation
`validate_candidate.py`	JSON schema validation for candidate results
`claim_issue.py`	Issue claim labels/comments (`--execute` uses `gh`)
`publish_pr.py`	Open PR (`--execute` uses `gh pr create`)
`merge_pr.py`	Fail-closed stub (merge not implemented)
`policy_gate.py`	Deterministic merge-policy evaluation
`github_state.py`	Label projection helpers
`collect_evidence.py`	Local git evidence snapshot

Coordinator entrypoints at repo scripts/:

team_coordinator.py: emit delegate_task specs
critique_candidates.py: blind ranking of candidate JSON
heavy_coding_flow.py: doctor + plan + worktree plan in one step

References

Read the bundled references before implementation:

references/candidate-protocol.md
references/repair-protocol.md
references/security-policy.md