review-release

Analyze GitHub repositories or releases via the GitHub API for static review.

5|1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/stefans71/FrontierBoard --skill review-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-release
Source: https://github.com/stefans71/FrontierBoard/tree/main/.claude/skills/review-release
Command: npx skills add https://github.com/stefans71/FrontierBoard --skill review-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify risks and quality issues in external GitHub repositories or releases before contributing or installing, without running any code.

Core Features & Use Cases

  • Static analysis only via the GitHub API
  • Two modes: Release review and Safety review
  • Check for related PRs and issues to avoid duplication

Quick Start

Provide a GitHub repo (owner/repo) and the desired review mode, then run the static analysis workflow against it.

Frequently Asked Questions about review-release

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

FAQPage Schema
How do I perform a static review of a GitHub repository before installing it?

To perform a static review of a GitHub repository, you provide the owner/repo name and select a review mode. The analysis fetches repo metadata, releases, PRs, and issues via the GitHub API to generate a comprehensive safety report without running any code.

What is static release analysis for public GitHub repos?

Static release analysis for public GitHub repos identifies risks and quality issues in external code before contributing or installing. It fetches diffs, PRs, and issues via the GitHub API to present a structured brief, ensuring no code execution is required.

Can I check for duplicate PRs and issues during a GitHub release review?

Yes, you can check for duplicate PRs and issues during a GitHub release review. The static analysis workflow specifically fetches related pull requests and issues to avoid duplication and guides decisions on potential contributions.

Does the GitHub safety review require running any code from the target repository?

No, the GitHub safety review does not require running any code from the target repository. It relies solely on static analysis via the GitHub API to fetch metadata, diffs, PRs, and issues to assess risks before installation.

What is the difference between a release review and a safety review for GitHub projects?

A release review targets specific GitHub releases to analyze diffs and metadata, while a safety review assesses any public repo or release for broader risks. Both modes use static GitHub API analysis to guide contribution or installation decisions.