land-review

Review code branches against tickets for acceptance criteria and scope.

1|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/bildzeitung/lode --skill land-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-review
Source: https://github.com/bildzeitung/lode/tree/main/.claude/skills/land-review
Command: npx skills add https://github.com/bildzeitung/lode --skill land-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the semantic review of code branches before they are merged, ensuring code quality and adherence to design principles.

Core Features & Use Cases

  • Semantic Code Review: Analyzes code branches against their tickets for adherence to acceptance criteria, scope, design invariants, and approach.
  • Automated Verdict: Provides a structured verdict of accept, bounce, or escalate based on the review findings.
  • Use Case: Before merging a branch, use this Skill to automatically review it against its ticket and receive a decision on whether it should be landed.

Quick Start

Run the land-review skill with the branch and ticket ID: land-review --branch land/lode-123 --ticket lode-123.

Frequently Asked Questions about land-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review against ticket acceptance criteria before merging a branch?

Automated branch review analyzes code branches against tickets to verify adherence to acceptance criteria, scope, design invariants, and approach. It requires access to both the branch and ticket details to perform a semantic code review.

What is the best way to check if a code branch meets its design invariants before landing?

Semantic code review checks code branches against their tickets for adherence to design invariants and approach. It evaluates scope and acceptance criteria to provide a structured verdict of accept, bounce, or escalate.

How do I run an automated branch review using a ticket ID?

Run the land-review skill with the branch and ticket ID, such as `land-review --branch land/lode-123 --ticket lode-123`. This automates the semantic review of code branches before they are merged.

Can I use automated semantic review to decide whether to accept, bounce, or escalate a branch?

Yes, automated semantic review provides a structured verdict of accept, bounce, or escalate based on the review findings. It analyzes the code branch against its ticket to ensure code quality and adherence to design principles.

What do I need to provide to perform an automated semantic code review before merging?

You need to provide the branch and ticket details to perform an automated semantic code review. The Skill requires access to both the branch and its associated ticket to check adherence to acceptance criteria and scope.

When should I use automated semantic review instead of manual code review for branch merging?

Use automated semantic review before merging code branches to ensure code quality and adherence to design principles without manual inspection. It automates the verification of acceptance criteria, scope, design invariants, and approach.