Aller au contenu
TakoAPI
Retour aux skills

pr-risk-analyzer

par nerdvana-labs

Git & GitHub
449Téléchargements rapportés par clawskills.sh
1Vues
0 mention J'aimeConnecte-toi pour aimer ce skill
—Pas encore noté
Ta note

Résumé

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

Description

Ce que fait ce skill

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.

Quand l'utiliser

  • 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

Exemple de workflow

ENTRÉE

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

SORTIE

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

Prérequis

  • GitHub personal access token (required for private repositories)

Installation

clawhub install nerdvana-labs/pr-risk-analyzer

Exécute la commande CLI, ou colle l'instruction dans Claude Code, Cursor, Codex ou l'agent de code que tu utilises.

Liens