Check Change Risk Before Opening a PR
check_change_riskCall this BEFORE opening a pull request, with the files you changed. Returns the deploy-risk score (0–100) the PR's Koalr check run will show, the reasons behind it, and toLower: ranked, concrete steps that lower the risk (for example, which files to split into their own PR), each with the score this change would drop to. Also names reviewers who know the code and how risky changes in this repository have gone lately. Get the file list with git diff --numstat <base>...HEAD (plus git diff --numstat for uncommitted work). If the result is medium or higher, take the top toLower step, call this again, and only then open the PR; mention the score and anything you chose not to fix in the PR description. Read-only: nothing about the change is stored.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"repository": "<repository>",
"files": "<files>"
},
"name": "check_change_risk"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| files | Yes | Every file the change touches (up to 300). | |
| title | No | Planned PR title. | |
| baseBranch | No | Branch the PR will target, e.g. "main". | |
| repository | Yes | GitHub repository as "owner/name", e.g. "acme/api-service". | |
| authorLogin | No | GitHub login of the person you are working for (`gh api user --jq .login`). Adds their history with these files to the score; without it, author expertise is not evaluated. | |
| description | No | Planned PR description. |