Review
Pre-landing review of a local diff, branch or PR for concrete defects, scope gaps and landing readiness, ending in SAFE TO LAND, LAND WITH CAUTION or DO NOT LAND. Use for 'review this', 'review my branch', 'is this safe to land' or 'check this diff'. To post comments on a GitHub PR use pr-review; for a security audit use review-security.
Install
/plugin marketplace add borkweb/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add borkweb/skills --skill reviewgit clone --depth 1 https://github.com/borkweb/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/gstack/review ~/.claude/skills/reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Pre-Landing Review Review the requested change for real defects and missing acceptance evidence. Default to report-only for a review request. Apply fixes only when requested or already authorized; never infer commit, push, merge or PR permission from a review invocation. ## Pin scope Identify the PR target or explicitly supplied base, then verify the ref exists. Use repository configuration/default branch only as a fallback, and disclose uncertainty. If needed and available, `../../../scripts/detect-base-branch.sh` resolves a candidate; its fallback is not proof. Resolve this path from the loaded skill directory, not an assumed Claude environment variable. Load the repo's rules ([repo-rules.md](../../core/do/references/repo-rules.md)) before reading the diff. When the brief or its criteria give a frozen `repo-rules-<slice>/` path, read only that copy, even when it is empty, and never the live store. Only when no frozen path is given (a standalone review), resolve the key with `node ../../core/do/repo-rules-key.mjs --dir <repo>` (a path relative to this skill's directory, like the one above) and read every `*.md` in the printed directory. A missing directory means no rules and is not an error. A key failure or an unreadable rule file is missing coverage: report it, and never treat it as zero rules. A rule violation is a finding that quotes the rule (file and condition) and the offending file:line, and takes the severity rules below.
Details
- Skill name
review- Repository
- borkweb/skills
- Path
skills/gstack/review/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Review skill do?
Pre-landing review of a local diff, branch or PR for concrete defects, scope gaps and landing readiness, ending in SAFE TO LAND, LAND WITH CAUTION or DO NOT LAND. Use for 'review this', 'review my branch', 'is this safe to land' or 'check this diff'. To post comments on a GitHub PR use pr-review; for a security audit use review-security.
How do I install the Review skill?
Claude Code plugin: /plugin marketplace add borkweb/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Review popular?
It lives in borkweb/skills, which has 9 GitHub stars and 0 forks.
Related skills
Prototype
9borkweb/skills
Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".
Agents Md Lint
9borkweb/skills
Audit and trim AI agent instruction files (AGENTS.md, CLAUDE.md, CONVENTIONS.md, .cursorrules, etc.) by testing which facts an AI agent can discover from code alone. Use when asked to lint, audit, optimize, prune, or trim any agent instruction file in a repository. Removes redundant documentation that wastes context tokens. Supports a dry-run mode that reports findings without modifying files.
Auto Scope
9borkweb/skills
Scopes a coding task before implementation — names the handful of files actually relevant (read/edit these), the areas to leave alone, and any open scope questions, so work doesn't start by reading the whole repo. Fires proactively at the start of substantive, multi-file, or unfamiliar-area work; stays silent on single-file edits, one-line fixes, questions, and continued work in an area already scoped this session. Use when beginning a feature, bug fix, or refactor that could plausibly touch several files or an area not yet seen this session.
App Store Changelog
9huytran1120/vietnam-agentic-skills
Generate user-facing App Store release notes from git history since the last tag.
PR Review
9borkweb/skills
Review a GitHub PR and post its CRITICAL findings as line-anchored inline comments with suggestion blocks after you confirm; INFORMATIONAL findings stay in chat. Adds a second pass from the other harness when the diff needs one, reuses CI results, and reviews only new commits on a re-run. Invoke only when the user explicitly asks for /pr-review or for a PR review that posts comments, or when bork:do runs a review batch; never on your own. For a local diff or branch without posting, use review.
Dialog Tree
3ikotelkin/claude-skills
Maintain a visual "dialog tree" — a data file plus a self-contained HTML viewer in the project repo that map the branches of a long conversation (user questions → the steps/variants of the answers) as an interactive tree with resolve/delete marks and a "built up to" marker for incremental updates. Use whenever the user asks to "create/set up a dialog tree", "update the tree", "add this to the tree", "show open branches", or mentions dialog-tree.html — and proactively offer it when a deep-dive discussion branches enough that the user risks losing track of unexplored side-threads.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.