Agent skill

App Review

by luxury-yacht in luxury-yacht/app

Audit broad Luxury Yacht systems or cross-cutting concerns for structural simplification, hardening, optimization, or refactoring; use for app-wide reviews and phased structural plans, not branch…

GPL-3.0Auto-check passedDevelopment

Install App Review

skills CLI
$ npx skills add luxury-yacht/app --skill app-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install luxury-yacht/app app-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/luxury-yacht/app.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/app-review .claude/skills/app-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
app-review
GitHub stars
444
Token cost
~818 tokens
SKILL.md length
386 words
Files
2 (incl. references)
Skills in repo
17
Repo updated
First seen
Licence
GPL-3.0

At a glance

Audit broad Luxury Yacht systems or cross-cutting concerns for structural simplification, hardening, optimization, or refactoring; use for app-wide reviews and phased structural plans, not branch…

  • Works in 4 steps: Inspect repository state read-only: git… → Name the review domains before judging… → Inventory each domain across producers,… → …
  • App-wide reviews and phased structural plans
  • SKILL.md covers Start, Review questions, Evidence per finding and Output, plus 2 more sections
  • Calls git

What it does

App Review is an agent skill from luxury-yacht/app. Audit broad Luxury Yacht systems or cross-cutting concerns for structural simplification, hardening, optimization, or refactoring; use for app-wide reviews and phased structural plans, not branch readiness or narrow bug scans

Its SKILL.md is about 820 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/settled-findings.md`).

It sits in Development, covering Customer feedback analysis and Refactoring. It works with Git. The repository describes itself as: Luxury Yacht - A cross-platform app for managing Kubernetes clusters and resources. The licence is GPL-3.0.

When your agent uses it

  • App-wide reviews and phased structural plans
  • Not branch readiness
  • Narrow bug scans

Example prompts

  • “/app-review”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Inspect repository state read-only: git status --short,
  2. Name the review domains before judging candidates; open owning architecture
  3. Inventory each domain across producers, consumers, tests, docs, and runtime
  4. Before proposing structural opportunities, read the

What it can do on your machine

Read from SKILL.md and the folder at commit 7001a03. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

App Review loads about 818 tokens when it runs, and up to ~1.5k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 386 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~818
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from luxury-yacht/app at commit 7001a03, republished under its GPL-3.0 licence (© luxury-yacht). 386 words, ~818 tokens.

Download SKILL.mdSave it as .claude/skills/app-review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
app-review
description
Audit broad Luxury Yacht systems or cross-cutting concerns for structural simplification, hardening, optimization, or refactoring; use for app-wide reviews and phased structural plans, not branch readiness or narrow bug scans

App Review

Audit whole systems deeply enough to find changes that remove a class of correctness, stability, consistency, performance, or development problems. Stay read-only unless the user explicitly requests planning or implementation.

Start

  1. Inspect repository state read-only: git status --short, git branch --show-current, git diff --stat, git ls-files --others --exclude-standard.
  2. Name the review domains before judging candidates; open owning architecture docs only after a domain is chosen.
  3. Inventory each domain across producers, consumers, tests, docs, and runtime paths. Use a narrow workflow skill only when deeper rules are needed.
  4. Before proposing structural opportunities, read the settled findings and reject candidates already consolidated, dismissed, or trigger-gated unless current evidence overturns that verdict.

Review questions

For each domain, determine:

  • every representation and owner of the state or contract;
  • producer/consumer ordering and boundary validation;
  • parallel implementations, compatibility branches, or duplicated definitions;
  • failure modes involving identity, freshness, lifecycle, permissions, teardown, or diagnostics;
  • whether tests prove the system contract or only local behavior; and
  • how many files, call sites, registrations, or user surfaces carry the pattern.

Prioritize correctness and data-safety risks, then cross-layer drift, simplification, app-wide pattern drift, and developer friction. Drop candidates supported only by one local example, naming/style preferences, or speculative rewrites.

Evidence per finding

  1. Current behavior or structure, with file references across the surface.
  2. Breadth, with counts or an explicit inventory.
  3. The concrete failure mode or recurring cost.
  4. What the change removes, centralizes, or makes explicit.
  5. The regression tests, diagnostics, docs, and skills affected.
Show full SKILL.md (135 more words)Show less

Output

When the user requests three areas, return exactly three ranked system-level areas, each with review domain, problem, impact, improvement direction, evidence, and likely validation. Rank by user-facing safety, breadth, change frequency, bug-class removal, and whether it unlocks other work. Answer follow-ups from gathered evidence and narrow architectural intent before implementation.

Plans and implementation

  • A requested plan is one temporary docs/plans/<topic>.md per independent area, or one plan for tightly coupled areas, with target model, non-goals, inventory, phased [ ] checklist, open questions, and validation. Keep temporary plans out of durable indexes.
  • Once implementation is authorized, work in dependency order and keep the plan current.

Boundaries

  • Use branch-review for merge readiness.
  • Not for a narrow bug or one-package improvement scan.
  • Do not delegate unless the user explicitly requests parallel agents.
  • Do not implement during an initial read-only review.

© luxury-yacht, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in .agents/skills/app-review of luxury-yacht/app.

  • SKILL.md
  • references/settled-findings.md

Open the folder on GitHubat commit 7001a03

Compare with similar skills

App Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

App Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
App Review this skillluxury-yacht/app444—~818Automated safety check: PassGPL-3.0
Codexskills-directory/skill-codex1.5k3 repos~1.8kAutomated safety check: PassMIT
Nexus MapperHaaaiawd/Nexus-skills166—~2.5kAutomated safety check: NotesNone
Refactoring Auditepam/ai-dial-chat504—~4.3kAutomated safety check: PassApache-2.0
Nexus QueryHaaaiawd/Nexus-skills166—~1.1kAutomated safety check: PassNone
Refactortermide/termide171—~2.8kAutomated safety check: PassMIT

Similar skills

  • Codex

    skills-directory/skill-codex

    A skill your agent uses when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing

    1.5k GitHub starsUsed in 3 repos~1.8k tokens
    DevelopmentAuto-check passed
  • Nexus Mapper

    Haaaiawd/Nexus-skills

    Generate a persistent .nexus-map/ knowledge base that lets any AI session instantly understand a codebase's architecture, systems, dependencies, and change hotspots.

    166 GitHub stars~2.5k tokensUpdated 6 mo ago
    DevelopmentAuto-check: notes
  • Refactoring Audit

    epam/ai-dial-chat

    Deep codebase refactoring audit for AI DIAL Chat. An agent skill from epam/ai-dial-chat.

    504 GitHub stars~4.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Nexus Query

    Haaaiawd/Nexus-skills

    Precise, instant code structure queries for active development — answer 'who depends on this interface before I refactor it', 'how many modules break if I change this', 'what is the real impact…

    166 GitHub stars~1.1k tokensUpdated 6 mo ago
    DevelopmentAuto-check passed
  • Refactor

    termide/termide

    Full-workspace code quality analysis and refactoring with validation

    171 GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Merge Master

    keybase/client

    A skill your agent uses when periodically merging upstream master commits into a long-running refactor branch where code has moved, been renamed, or restructured — guiding careful per-commit…

    9.3k GitHub stars~1.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from luxury-yacht/app

All 17 skills in this repo
  • Improve Backend

    luxury-yacht/app

    A skill your agent uses when wanting to systematically improve the Go backend - scans for security vulnerabilities, stability risks, performance issues, and code simplification opportunities, then…

    444 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Improve Frontend

    luxury-yacht/app

    A skill your agent uses when wanting to systematically improve the React/TypeScript frontend - scans for security vulnerabilities, stability risks, performance issues, and code simplification…

    444 GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Eliminate representable-but-invalid Luxury Yacht states with discriminated unions, required identity, typed status, validated constructors, or one boundary chokepoint; use for "make impossible…

    444 GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • Add Resource

    luxury-yacht/app

    Add or extend support for a Kubernetes resource kind across the required catalog, refresh, detail, object-panel, object-map, permission, documentation, and test surfaces

    444 GitHub stars~704 tokensUpdated today
    Auto-check passed
  • Browse Tables

    luxury-yacht/app

    Change cluster or namespace views, Browse/catalog surfaces, shared GridTable behavior, filters, pagination, large datasets, metrics columns, or refresh-backed resource tables

    444 GitHub stars~518 tokensUpdated today
    Auto-check passed
  • Refresh Subsystem

    luxury-yacht/app

    Modify Luxury Yacht refresh domains, snapshots, streams, doorbells, polling fallback, diagnostics, retained data, or refresh lifecycle while preserving cross-layer ordering and recovery contracts

    444 GitHub stars~563 tokensUpdated today
    Auto-check passed

Works with

Questions about App Review

What does App Review do?

Audit broad Luxury Yacht systems or cross-cutting concerns for structural simplification, hardening, optimization, or refactoring; use for app-wide reviews and phased structural plans, not branch…. App Review is an agent skill from luxury-yacht/app.

When should I use App Review?

App Review fits situations like: app-wide reviews and phased structural plans; not branch readiness; narrow bug scans.

How do I install App Review in Claude Code?

Run `npx skills add luxury-yacht/app --skill app-review -a claude-code`. Or copy the skill folder (.agents/skills/app-review in luxury-yacht/app) into .claude/skills/app-review in your project. Claude Code loads it when a task matches its description.

How do I install App Review in Codex?

Run `npx skills add luxury-yacht/app --skill app-review -a codex`. Or copy the skill folder (.agents/skills/app-review in luxury-yacht/app) into .agents/skills/app-review in your project. Codex loads it when a task matches its description.

Can I use App Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add luxury-yacht/app --skill app-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/app-review, .gemini/skills/app-review, .github/skills/app-review and .opencode/skills/app-review in your project.

What does App Review need to run?

Going by SKILL.md and its folder, App Review needs the command-line tools its instructions call (git).

Does App Review access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is App Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does App Review use?

App Review is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does App Review use?

About 818 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 695 tokens, read only when the agent opens those files.

What are the alternatives to App Review?

Skills that share tags, products or a category with App Review: Codex (skills-directory/skill-codex, 1.5k stars), Nexus Mapper (Haaaiawd/Nexus-skills, 166 stars), Refactoring Audit (epam/ai-dial-chat, 504 stars) and Nexus Query (Haaaiawd/Nexus-skills, 166 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains App Review?

luxury-yacht (a GitHub organization) maintains it in luxury-yacht/app, which has 444 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 10, 2026.

Source: luxury-yacht/app on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.