Skip to content

feat(workflows): add /change-risk slash command for PR risk assessment#434

Merged
jamesadevine merged 1 commit into
mainfrom
risk-check-agent
May 7, 2026
Merged

feat(workflows): add /change-risk slash command for PR risk assessment#434
jamesadevine merged 1 commit into
mainfrom
risk-check-agent

Conversation

@jamesadevine
Copy link
Copy Markdown
Collaborator

Summary

Adds a new /change-risk slash command workflow that performs on-demand breaking-change risk assessments on pull requests.

What it does

When a user comments /change-risk on a PR, the agent:

  1. Fetches the full PR diff via GitHub MCP tools
  2. Analyzes changes across five risk categories:
    • Public API surface — signature changes, removed items
    • Behavioral changes — altered defaults, error handling, serialization
    • Pipeline output — template markers, generated YAML structure
    • Cross-cutting concerns — shared types, CLI args, path handling
    • Dependency & build impact — Cargo.toml changes, feature flags
  3. Submits a formal PR review (APPROVE or REQUEST_CHANGES) with a structured risk assessment — not just a comment

Files

File Purpose
.github/workflows/change-risk.md Workflow source (frontmatter + agent prompt)
.github/workflows/change-risk.lock.yml Compiled GitHub Actions workflow
.github/aw/actions-lock.json Updated action SHA pins (auto-generated)

Testing

  • Compiled with gh aw compile change-risk --strict — 0 errors, 0 warnings

Add an on-demand agentic workflow triggered by /change-risk on pull
requests. The agent analyses the diff for breaking API changes,
behavioral shifts, pipeline output changes, and dependency impact,
then submits a formal PR review (APPROVE or REQUEST_CHANGES).

Co-authored-by: Copilot <[email protected]>
@jamesadevine jamesadevine merged commit e787956 into main May 7, 2026
12 checks passed
@jamesadevine jamesadevine deleted the risk-check-agent branch May 7, 2026 10:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant