Skip to content
TakoAPI
Back to skills

pr-risk-analyzer

by nerdvana-labs

Git & GitHub
449Downloads reported by clawskills.sh
1Views
0 likesSign in to like this skill
—Not yet rated
Your rating

Brief

Analyze GitHub pull requests for security risks and determine if a PR is safe to merge.

Description

What This Skill Does

Evaluates a GitHub pull request for security risks before merging. Checks for exposed secrets, large diffs, and sensitive file modifications. Returns a risk score, flagged issues, and a merge recommendation.

Surfaces security and scope issues in a PR without manually reading every diff or running a separate SAST tool.

When to Use It

  • Checking if a dependency update PR introduces secrets
  • Reviewing a contractor's PR before merging to main
  • Scanning a large refactor for risky file changes
  • Quick pre-deployment PR audit in a CI review process
  • Flagging high-risk PRs in a busy open source repo

Example Workflow

INPUT

User asks: Is PR #142 in acme-org/backend safe to merge?

AGENT
  1. 1

    Identify repo as acme-org/backend and PR number as 142

  2. 2

    Ask user for GitHub token if repo is private

  3. 3

    POST to pr-risk-analyzer.onrender.com/analyze-pr with repo, pr_number, and token

  4. 4

    Parse riskScore, riskLevel, issues, and summary from response

  5. 5

    Present risk level, bullet-pointed issues, and a clear merge recommendation

OUTPUT

Risk level: Medium. Issues: hardcoded API key in config.js, 1,200 lines changed across 34 files. Recommendation: Needs review before merging.

Requirements

  • GitHub personal access token (required for private repositories)

Installation

clawhub install nerdvana-labs/pr-risk-analyzer

Run the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.

Links