Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Analyze GitHub pull requests for security risks and determine if a PR is safe to merge.
Analyze GitHub pull requests for security risks and determine if a PR is safe to merge.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Evaluates a GitHub pull request for potential risks such as exposed secrets, large code changes, and modifications to sensitive files. Provides a risk score and recommendation before merging.
Use this skill when a user asks to: Check if a PR is safe to merge Analyze a pull request Scan a PR for security or risk Review changes before deployment
Repository (owner/repo) Pull request number GitHub access token (required for private repositories) If any input is missing, ask the user for it.
Identify repository and PR number from the user request. If the repository is private, request a GitHub access token. Send a POST request to: https://pr-risk-analyzer.onrender.com/analyze-pr Body: { "repo": "<owner/repo>", "pr_number": <number>, "github_token": "<token if available>" } Parse the response: riskScore riskLevel issues summary Respond to the user with: Risk level Key issues (bullet points) Clear recommendation: Safe to merge Needs review High risk โ do not merge
Do not guess repository or PR number. If API fails, inform the user and suggest retry. Do not expose or store GitHub tokens. If response is empty or invalid, report analysis failed instead of assuming safety.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.