Spot release risks before your code is merged.
Produces a pre-merge risk report to help users decide whether code changes are ready to ship.
When to use it
Use before merging when the user wants changes reviewed for risk, correctness, or rollback problems.
Give it a PR, MR, or repository reference; it asks which analysis to run, saves a Markdown report, and offers fixes.
What you provide
The main workflow requires the remote server's review creation, task status, journal, and report tools; a CLI fallback is documented.
For SigV4 authentication, invoke this skill first when list_agent_spaces is available and orchestration has not already run this session.
This skill
GitHub
Pushes branches to GitHub
GitLab
Pushes branches to GitLab