skills.rest
luxury-yacht
luxury-yachtOFFICIAL
Explore all skills by this author →
GitHub

branch-review

Audit Luxury Yacht branches for merge and production readiness using git diff and contracts.

411|21|Updated Dec 18, 2025
Search Tags:#git#code review#production readiness#merge validation#branch readiness#architecture contracts#Kubernetes desktop app
One-click install
npx skills add https://github.com/luxury-yacht/app --skill branch-review-luxury-yacht
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch-review
Source: https://github.com/luxury-yacht/app/tree/main/.agents/skills/branch-review
Command: npx skills add https://github.com/luxury-yacht/app --skill branch-review-luxury-yacht

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps determine whether a Luxury Yacht branch is merge-ready, production-ready, and PR-summary quality by grounding the assessment in the actual diff and the repo’s internal contracts.

Core Features & Use Cases

  • Merge readiness verdict: Produces a concrete go/no-go-style assessment based on code changes, tests, and validation state, prioritizing findings over narrative.
  • Contract audit by change area: Reviews meaningful changes against the relevant architecture and skill contracts to ensure correctness across multi-cluster behavior, refresh/streams, identity/resource modeling, permissions, and UI data handling.
  • Validation-driven confidence: Recommends and sequences focused checks and requires specific validation steps (including mage qc:prerelease and git diff --check) before declaring “ready” for non-documentation work.

Quick Start

Ask: “Review the current branch for merge readiness using origin/main...HEAD and give me findings with exact file/line details, then state the validation state and residual risk.”

Frequently Asked Questions about branch-review

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

FAQPage Schema
How do I check if a git branch is ready for a production merge?▼

A merge-readiness review assesses your git diff against repository contracts to produce a go/no-go verdict. It audits change areas for architecture correctness across multi-cluster behavior, identity modeling, and UI data handling, requiring validation commands like mage qc:prerelease before declaring production readiness.

What is a contract audit for code review?▼

A contract audit for code review validates branch changes against repository architecture contracts. It verifies correctness across boundaries including multi-cluster behavior, refresh streams, identity and resource modeling, permissions, and UI data handling before a production merge.

How do I validate a PR summary against the actual git diff?▼

Validating a PR summary against the actual git diff requires a read-only first pass to inspect git status and changes. The review grounds the PR summary in real file and line details, producing structured findings, open questions, and a final merge verdict based on validation state and residual risk.

What validation commands are required before declaring a branch merge-ready?▼

Before declaring a branch merge-ready for non-documentation work, you must run specific validation steps including mage qc:prerelease and git diff --check. These commands sequence focused checks to ensure the branch meets production-readiness and architecture contract requirements.

Can I use a standard code review for Kubernetes desktop app architecture changes?▼

Standard code reviews often lack the specific contract audits needed for Kubernetes desktop app architecture changes. A targeted merge-readiness review evaluates multi-cluster behavior, refresh streams, and identity modeling against repository contracts to ensure cross-boundary correctness before merging.

Related Skills

Explore More Software Engineering Skills→
hairpin01hairpin01
3

git-safe-operator

Inspect git repository status and diffs to prepare safe commit plans.

Community
Intermediate
KentoShimizuKentoShimizu
7

release-management

Automate release governance with auditable go/no-go decision records.

Community
Intermediate
Pact-Community-OrganizationPact-Community-Organization
1

pact-invariants

Define Pact schema invariants and behavioral properties for smart-contract verification.

Official
Intermediate
nodatallnodatall
2

merge-review

Automate branch merge-readiness reviews against the main branch diff.

Community
Advanced