code-check-release-risk

To check release risk before shipping, analyze the branch diff against the base branch to categorize changes into risk buckets like API compatibility, database schema, auth, and environment configuration. This produces a concise pre-publish briefing without blocking the publish step.

A pre-publish release risk briefing summarizes what changed in a branch and highlights what could break after a push, PR, or release. It classifies diff content into defined risk categories to help teams avoid production regressions before publishing.

Detect schema migration and auth regression risks by evaluating the git diff between the base branch and HEAD. This classifies persistence schema and authentication changes into targeted risk buckets to highlight potential operational drift before release.

A release risk briefing does not block your deployment workflow. It provides non-blocking guidance by outputting a concise overall risk assessment and recommending follow-up actions for doc sync or changelog updates without preventing the publish step.

You can analyze environment variable changes and rollback concerns by categorizing branch diff content into new environment setup and rollback planning buckets. This ensures operational and document drift are detected and included in the risk assessment.