Saltar al contenido
TakoAPI
Volver a skills

pr-risk-analyzer

por nerdvana-labs

Git & GitHub
449Descargas según clawskills.sh
1Vistas
0 me gustaInicia sesión para dar me gusta a esta skill
—Aún sin valoraciones
Tu valoración

Resumen

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

Descripción

Qué hace esta 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.

Cuándo usarla

  • 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

Flujo de trabajo de ejemplo

ENTRADA

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

AGENTE
  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

SALIDA

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

Requisitos

  • GitHub personal access token (required for private repositories)

Instalación

clawhub install nerdvana-labs/pr-risk-analyzer

Ejecuta el comando de la CLI o pega el prompt en Claude Code, Cursor, Codex o el agente de programación que uses.

Enlaces