land

Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly actionable skill body with clear sequencing and validation for a destructive merge workflow. Its main weaknesses are length/redundancy (the preflight is explained in three places) and a monolithic structure that does not progressively disclose detail into separate files.

Suggestions

Consolidate the fast-path preflight into one place: keep the executable command in the Commands block and have Steps and the 'Fast Path Preflight' section reference it instead of re-describing the conditions and exit codes each time.

Move the long 'Review Handling' and 'Failure Handling' sections into separate reference files (e.g. REVIEW_HANDLING.md, FAILURE_HANDLING.md) and link to them from the main body, so SKILL.md stays an overview.

Tighten prose by removing restated watcher exit codes and prefacing only the non-obvious behaviors (e.g. the auto-fix commit force-push flow) rather than re-explaining each in multiple sections.

Dimension	Reasoning	Score
Conciseness	Mostly actionable rather than explanatory, but the body is long and repeats the fast-path preflight across Steps, the Commands block, and the 'Fast Path Preflight' section, and restates watcher exit codes twice. It could be tightened without losing meaning.	2 / 3
Actionability	Provides concrete, copy-paste-ready shell (gh pr view/merge, git diff --check, ruff/pytest/npm commands) and the exact land_watch.py invocations with flags and exit codes — fully executable guidance.	3 / 3
Workflow Clarity	A numbered multi-step sequence with explicit validation checkpoints (git diff --check, ruff/pytest, watch checks until green), a fast-path vs conservative-fallback branch, and feedback loops (fix -> commit -> push -> re-run) for the destructive merge operation.	3 / 3
Progressive Disclosure	Well-organized into labeled sections, but it is a single monolithic ~330-line file with no bundle references; detailed Review Handling and Failure Handling content that could live in separate files is inline, so structure is present but not split.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, third-person description that names concrete landing actions and gives an explicit use-when trigger with natural keywords. It cleanly answers both what and when with no fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'monitoring conflicts, resolving them, waiting for checks, and squash-merging when green' — matching the anchor for several specific concrete actions.	3 / 3
Completeness	Explicitly states what it does (land a PR via the listed actions) and when to use it via an explicit 'use when' clause, satisfying both halves.	3 / 3
Trigger Term Quality	'use when asked to land, merge, or shepherd a PR to completion' covers natural terms a user would actually say (land, merge, shepherd a PR).	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (landing/merging PRs) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: karanhudia/borg-ui
Path: .codex/skills/land/SKILL.md
Commit: 380827d

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.