القائمة
Merge an archived candidate after explicit human approval and complete required post-merge bookkeeping.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Drive an approved tracked plan through implementation, validation, independent review, archive, publish, CI/sync evidence, and readiness to wait for merge approval.
Create or update the tracked root plan and, for coordinated work, its agent-owned subplans.
Drive an approved tracked plan through implementation, validation, independent review, archive, publish, CI/sync evidence, and readiness to wait for merge approval.
Create or update the tracked root plan and, for coordinated work, its agent-owned subplans.
Clarify a harness task before planning when the objective, boundaries, tradeoffs, success criteria, or workflow direction are genuinely unclear. Do not use for factual repo questions, status checks, or approved execution.
Clarify a harness task before planning when the objective, boundaries, tradeoffs, success criteria, or workflow direction are genuinely unclear. Do not use for factual repo questions, status checks, or approved execution.
استنادا إلى تصنيف SOC المهني
| name | harness-land |
| description | Merge an archived candidate after explicit human approval and complete required post-merge bookkeeping. |
| metadata | {"easyharness-managed":"true","easyharness-version":"dev"} |
Use this skill only after the human explicitly approves merge and harness status reports execution/finalize/await_merge. If the candidate is no longer
valid, reopen it and return to harness-execute instead of merging.
Verify the recorded PR, current CI, sync, and mergeability facts.
Merge using the repository's preferred strategy unless the human specifies another.
Immediately record merge confirmation, before local branch cleanup or checkout changes. Squash, rebase, and merge-commit strategies selected by the repository are all valid:
harness land --pr <url> [--commit <sha>]
Rely on the forge's merge record by default. Add a PR comment or issue update only when unresolved or partial work, deployment or release results, or material post-merge context needs a durable handoff. Close fully resolved issues when that is semantically correct and the forge has not already done so; leave explicit pointers for partial or deferred work.
Finish local branch cleanup and sync.
Run harness land complete only after required bookkeeping is done. Confirm
harness status returns to idle with landed context preserved.
Do not merge without explicit approval, edit the archived plan to add merge metadata, manufacture a no-information land comment, silently close partial issues, or complete land before its durable bookkeeping is finished.