catu-ai/harness-land
assets/bootstrap/skills/harness-land/SKILL.md
Use when a tracked harness plan is already archived and the human has explicitly approved merge, so the agent should merge the PR and complete the required post-merge bookkeeping.
$ install --global
skillsauthnpx skillsauth add catu-ai/easyharness harness-landInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:56 PM1.7s1 file scanned
SKILL.md
- name:
- harness-land
- description:
- Use when a tracked harness plan is already archived and the human has explicitly approved merge, so the agent should merge the PR and complete the required post-merge bookkeeping.
Harness Land
Purpose
Use land only after the plan is archived and a human has said it is time to merge.
Workflow
-
Run
harness status. -
If
state.current_nodeis notexecution/finalize/await_merge, stop.- If the candidate is no longer valid, run
harness reopen --mode finalize-fixfor narrow repair orharness reopen --mode new-stepwhen the change deserves a new step, and then return toharness-execute. - If the plan is still executing, stay in
harness-execute.
- If the candidate is no longer valid, run
-
Re-read the
Pre-Landscan in ../harness-execute/references/controller-truth-surfaces.md so merge readiness, CI truth, and required bookkeeping are freshly checked. -
Verify the PR still looks merge-ready.
-
Merge the PR.
-
Prefer
Merge commitunless the human explicitly asks for a different strategy. -
Run:
harness land --pr <url> [--commit <sha>]This records merge confirmation and enters required post-merge bookkeeping.
-
Finish the required post-merge bookkeeping before leaving
land.- Add a final PR comment when the permanent PR record still needs a durable merge closeout note or follow-up handoff after the merge.
- The minimum PR comment content is:
- confirmation that the PR merged
- the merged commit or merge reference when it is available
- whether linked issues were closed or intentionally left open
- any durable follow-up pointer that a later reader needs
- Close a linked issue when the merged change fully resolves it.
- If a linked issue is only partially addressed, intentionally deferred, or still needs later work, do not close it silently; add or update the issue with a follow-up reference to the merged PR and the remaining work.
-
Finish local cleanup, branch sync, and any final remote follow-up.
-
Run:
harness land complete
Run this only after the required PR and issue bookkeeping is complete. This
records required post-merge bookkeeping completion, clears the current
candidate pointer, and
records the last landed archived plan so harness status returns to idle
with the landed context preserved in artifacts.
11. Sync local main, delete the feature branch if appropriate, and leave the
worktree clean.
Do Not
- Do not merge without explicit human approval.
- Do not edit the archived plan after merge just to record merge metadata.
- Do not skip the explicit land milestones; run
harness land --pr <url>after merge andharness land completeafter the required bookkeeping so status stops reporting the archived candidate as current work. - Do not treat PR comments, linked-issue closure, or linked-issue follow-up as optional best-effort cleanup when they are needed for the permanent record.
- Do not keep using
landif the candidate is no longer valid; switch back toharness-executeviaharness reopen --mode <finalize-fix|new-step>.
Related Skills
catu-ai/harness-reviewer
documentation
VerifiedTrustedCommunity
Use when acting as a dedicated reviewer subagent for one assigned harness review slot in an existing review round and you need to inspect the change, write structured findings, and submit them through `harness review submit`. This skill is only for reviewer subagents, not for the controller agent.
10SKILL.mdUpdated Apr 16, 2026
catu-ai/harness-plan
data-ai
VerifiedTrustedCommunity
Create or update a tracked harness plan once the direction is clear enough to execute. Use this when work needs a self-contained plan that a future agent can complete from the repository alone, without relying on discovery chat or hidden session memory.
10SKILL.mdUpdated Apr 16, 2026
catu-ai/harness-execute
testing
VerifiedTrustedCommunity
Use when a tracked harness plan has been approved and the controller agent should drive implementation, review, archive closeout, publish/CI/sync evidence work, and merge-readiness follow-up until the archived candidate is genuinely ready to wait for merge approval. This is the main controller skill for day-to-day execution after approval.
10SKILL.mdUpdated Apr 16, 2026
catu-ai/harness-discovery
testing
VerifiedTrustedCommunity
Run interactive, Socratic discovery before planning or execution when the objective, boundaries, tradeoffs, success criteria, size, or workflow direction are unclear, or when archived work may need to reopen. Do not use for casual Q&A, simple repo orientation, status checks, or already-approved execution.
10SKILL.mdUpdated Apr 16, 2026