skills.rest
AgentSystemLabs
AgentSystemLabsOFFICIAL
Explore all skills by this author →
GitHub

check-release-risk

Analyze branch diffs to categorize release-breaking changes by risk.

121|2|Updated Apr 24, 2026
Search Tags:#database migrations#api changes#git diff#rollback planning#release risk#auth changes#pre-publish review
One-click install
npx skills add https://github.com/AgentSystemLabs/core --skill check-release-risk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: check-release-risk
Source: https://github.com/AgentSystemLabs/core/tree/main/plugins/agentsystem-core/skills/check-release-risk
Command: npx skills add https://github.com/AgentSystemLabs/core --skill check-release-risk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents painful production surprises by summarizing what in your branch diff could break behavior, integrations, deployment, or rollback safety before you push, open a PR, or create a release.

Core Features & Use Cases

  • Production risk briefing from branch diffs: Summarizes commits and file changes relative to the resolved base branch, focusing on what changed and why it might matter in production.
  • Change categorization for actionable risk: Classifies findings into public API changes, persistence/migration shape changes, auth/payment/permission changes, new env/operational setup, manual-QA-needed paths, doc/changelog drift, and rollback concerns.
  • Informational, not gating: Reports risks with recommendations and “overall risk” (LOW/MEDIUM/HIGH) while explicitly not blocking the user’s publish actions.

Quick Start

Run the check by telling the AI: “Summarize the release risk for this branch and what could break in production.”

Frequently Asked Questions about check-release-risk

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

FAQPage Schema
How do I check release risk from a git branch diff before pushing?▼

To check release risk from a git branch diff, analyze the committed changes against the resolved base branch to identify potential breaks in public APIs, persistence layers, auth, and rollback safety before you push.

What is a pre-publish review for release-breaking changes?▼

A pre-publish review for release-breaking changes is an analysis of branch commits that categorizes risks across API surfaces, database migrations, and operational setups to prevent production surprises before releasing.

How do I categorize API and database migration risks before a release?▼

Categorize API and database migration risks by inspecting the branch diff to classify changes into public API modifications, persistence shape changes, manual-QA-needed paths, and doc or changelog drift.

Can I get a rollback planning briefing from unmerged git commits?▼

Yes, you can generate a rollback planning briefing from unmerged git commits by analyzing the diff for persistence, migration, and permission changes that could impact rollback safety in production.

Does the release risk analysis block my publish actions if it finds auth changes?▼

No, the release risk analysis is informational and does not block your publish actions; it reports auth changes and overall risk levels with recommendations while explicitly allowing you to proceed.

What types of production risks should I look for in a pre-publish git diff?▼

Look for production risks in a pre-publish git diff by checking for public API changes, new environment setups, auth or payment permission modifications, manual-QA-needed workflows, and changelog drift.

Related Skills

Explore More Software Engineering Skills→
jayteealaojayteealao

review:quick

Automate structured code reviews by analyzing git diffs with five checklists.

Community
Basic
leifericfleifericf
5

assess-risk

Automate pre-deployment risk assessment and rollback planning for software changes.

Community
Intermediate
Rune-kitRune-kit
82

db

Generate and validate database schema migrations for ORMs and raw SQL.

Official
Advanced
julianobarbosajulianobarbosa
7

reviewing-code

Review code for quality, bugs, security issues, and best practices using Codex.

Community
Advanced