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.
83
75%
Does it follow best practices?
Impact
95%
1.90xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.codex/skills/land/SKILL.mdReview comment handling workflow
[codex] prefix on all replies
0%
100%
Per-comment mode stated
70%
100%
Comment classification
10%
100%
Pushback template used
100%
100%
Conflict with user intent flagged
100%
100%
Clarify mode for vague comment
100%
100%
Inline vs issue thread routing
100%
100%
Single consolidated root-level update
100%
100%
Root-level update prefixed [codex]
0%
100%
Reply before change principle
50%
80%
PR landing script implementation
Squash merge flag
75%
100%
PR title as merge subject
100%
100%
PR body as merge body
0%
100%
No auto-merge
50%
100%
No branch deletion step
0%
100%
Watcher script preferred
0%
100%
Watcher exit codes handled
0%
70%
Mergeability check
100%
100%
CI log commands
0%
16%
PR conflict and CI failure runbook
Conflict: fetch and merge main
60%
100%
Conflict: push after resolution
100%
100%
Auto-fix: detect head change
30%
100%
Auto-fix: pull bot commit
100%
100%
Auto-fix: add real author commit
50%
100%
Auto-fix: force-push to retrigger CI
12%
100%
Force-with-lease used
100%
100%
Lockfile: fetch and merge main
20%
100%
Lockfile: force-push and rerun CI
50%
100%
Mergeability UNKNOWN: wait
0%
100%
Merge-conflict mergeability check
83%
100%
4cbe3a9
Table of Contents
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.