New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Gstack Pre-Landing Review

by LING71671 in LING71671/Open-ClaudeCode

Runs a staff-engineer style review over the current diff before merging, listing findings by severity with file, impact and a suggested fix.

Custom licenceAuto-check: notesDevelopment

Install Gstack Pre-Landing Review

skills CLI
$ npx skills add LING71671/Open-ClaudeCode --skill gstack-review -a claude-code

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

GitHub CLI
$ gh skill install LING71671/Open-ClaudeCode gstack-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/LING71671/Open-ClaudeCode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/gstack-workflows/skills/gstack-review .claude/skills/gstack-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
gstack-review
GitHub stars
960
Token cost
~316 tokens
SKILL.md length
149 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
Custom licence

At a glance

Runs a staff-engineer style review over the current diff before merging, listing findings by severity with file, impact and a suggested fix.

  • Works in 5 steps: Inspect repository state with git status… → Identify the base diff with git diff… → Read the changed code and its immediate… → …
  • Reviewing a branch before merging or shipping
  • SKILL.md covers Workflow, Review Priorities and Output
  • Calls git

What it does

A review pass over the current branch or diff before it lands. The agent checks repository state with `git status --short`, finds the base diff with `git diff --stat`, reads the changed code and its immediate callers, and looks for behavioral regressions, security boundaries, error-handling gaps, state persistence bugs and missing tests. It then runs, or names, the narrowest verification command that fits the changed area.

Priorities include correctness and edge cases, trust boundaries, data loss and migration risk, handling of long-running processes, provider and protocol compatibility, test coverage in proportion to risk, and docs that drift when user-facing behavior changes. Output leads with findings ordered by severity, each with file and line when available, impact, why it can happen and a suggested fix. When nothing is found, the review says so and lists remaining test gaps or residual risk.

When your agent uses it

  • Reviewing a branch before merging or shipping
  • Checking whether a change is safe to land
  • Getting a severity-ordered findings list for a diff

Example prompts

  • “Do a pre-landing review of my current branch.”
  • “Is this diff safe to merge? Look at the changed files and their callers.”
  • “Review my uncommitted changes and rank the problems by severity.”

Requirements

  • A Git repository with a diff to review
  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Bash

Workflow steps

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

  1. Inspect repository state with git status --short.
  2. Identify the base diff with git diff --stat and the focused changed files.
  3. Read the changed code and its immediate callers.
  4. Look for behavioral regressions, security boundaries, error handling gaps, state persistence bugs, and missing tests.
  5. Run or identify the narrowest verification command that matches the changed surface.

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob
    • Bash

    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

Gstack Pre-Landing Review loads about 316 tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 149 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~35
When it runs · the whole SKILL.md, loaded when a task matches
~316

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Grep, Glob, Bash

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 149 words (~316 tokens).

“Use this skill as a staff-engineer review pass over the current diff.”

— opening of SKILL.md by LING71671, Custom licence
name
gstack-review
allowed-tools
Read, Grep, Glob, Bash

Read the full SKILL.md on GitHub

Files

Just SKILL.md in plugins/gstack-workflows/skills/gstack-review of LING71671/Open-ClaudeCode.

Open the folder on GitHubat commit 2980105

Compare with similar skills

Gstack Pre-Landing 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.

Gstack Pre-Landing Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Gstack Pre-Landing Review this skillLING71671/Open-ClaudeCode960—~316Automated safety check: NotesCustom licence
Requesting Code ReviewHezaoHezao/poirot2505 repos~1.6kAutomated safety check: PassMIT
Pre-PR Reviewyuga-hashimoto/and-code123—~710Automated safety check: PassMIT
PR Deep VerificationQwenLM/qwen-code28k—~18kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything85k1 repos~1.4kAutomated safety check: PassMIT

Similar skills

  • Requesting Code Review

    HezaoHezao/poirot

    Pre-commit review: security scan, quality gates, auto-fix. An agent skill from HezaoHezao/poirot.

    250 GitHub starsUsed in 5 repos~1.6k tokens
    DevelopmentAuto-check passed

  • Pre-PR Review

    yuga-hashimoto/and-code

    Runs local checks and a repo-reviewer subagent over the whole branch diff before a pull request is opened, then records the approval in the PR description.

    123 GitHub stars~710 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • PR Deep Verification

    QwenLM/qwen-code

    Runs a sandboxed, evidence-based check of one qwen-code pull request, proving its main change against the base build and writing a report with a machine-readable verdict.

    28k GitHub stars~18k tokensUpdated today
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    85k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

  • Open Code Review CLI

    alibaba/open-code-review

    Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.

    44k GitHub stars~3.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

More from LING71671/Open-ClaudeCode

  • Gstack Document Release

    LING71671/Open-ClaudeCode

    Brings project documentation back in line with shipped behavior by reading the current diff for user-visible changes and updating only the docs they affect.

    960 GitHub stars~282 tokensUpdated 2 mo ago
    Auto-check: notes

  • Root-Cause Investigation Workflow

    LING71671/Open-ClaudeCode

    Diagnoses a bug, crash, regression or flaky behavior by reproducing it and testing several causes before applying the smallest fix.

    960 GitHub stars~322 tokensUpdated 2 mo ago
    Auto-check: notes

  • Gstack Cso

    LING71671/Open-ClaudeCode

    Security audit workflow for OPC code, providers, plugins, Electron surfaces, local HTTP bridges, filesystem access, and command execution.

    960 GitHub stars~321 tokensUpdated 2 mo ago
    Auto-check: notes

  • Gstack QA Only

    LING71671/Open-ClaudeCode

    Read-only QA report for an OPC desktop flow, CLI command, local URL, staging URL, or documented user journey.

    960 GitHub stars~282 tokensUpdated 2 mo ago
    Auto-check: notes

Works with

Categories

Questions about Gstack Pre-Landing Review

What does Gstack Pre-Landing Review do?

Runs a staff-engineer style review over the current diff before merging, listing findings by severity with file, impact and a suggested fix. A review pass over the current branch or diff before it lands. The agent checks repository state with `git status --short`, finds the base diff with `git diff --stat`, reads the changed code and its immediate callers, and looks for behavioral regressions, security boundaries, error-handling gaps, state persistence bugs and missing tests.

When should I use Gstack Pre-Landing Review?

Gstack Pre-Landing Review fits situations like: reviewing a branch before merging or shipping; checking whether a change is safe to land; getting a severity-ordered findings list for a diff.

How do I install Gstack Pre-Landing Review in Claude Code?

Run `npx skills add LING71671/Open-ClaudeCode --skill gstack-review -a claude-code`. Or copy the skill folder (plugins/gstack-workflows/skills/gstack-review in LING71671/Open-ClaudeCode) into .claude/skills/gstack-review in your project. Claude Code loads it when a task matches its description.

How do I install Gstack Pre-Landing Review in Codex?

Run `npx skills add LING71671/Open-ClaudeCode --skill gstack-review -a codex`. Or copy the skill folder (plugins/gstack-workflows/skills/gstack-review in LING71671/Open-ClaudeCode) into .agents/skills/gstack-review in your project. Codex loads it when a task matches its description.

Can I use Gstack Pre-Landing 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 LING71671/Open-ClaudeCode --skill gstack-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/gstack-review, .gemini/skills/gstack-review, .github/skills/gstack-review and .opencode/skills/gstack-review in your project.

What does Gstack Pre-Landing Review need to run?

Going by SKILL.md and its folder, Gstack Pre-Landing Review needs the command-line tools its instructions call (git). Our summary lists: A Git repository with a diff to review. Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash.

Does Gstack Pre-Landing 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 Gstack Pre-Landing Review safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Gstack Pre-Landing Review use?

Gstack Pre-Landing Review has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Gstack Pre-Landing Review use?

About 316 tokens (SKILL.md is roughly 1.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gstack Pre-Landing Review?

Skills that share tags, products or a category with Gstack Pre-Landing Review: Requesting Code Review (HezaoHezao/poirot, 250 stars), Pre-PR Review (yuga-hashimoto/and-code, 123 stars), PR Deep Verification (QwenLM/qwen-code, 28k stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gstack Pre-Landing Review?

LING71671 (a GitHub user) maintains it in LING71671/Open-ClaudeCode, which has 960 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on July 22, 2026.

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