github-validate-pr

Analyze GitHub pull requests for checks, blockers, and security signals to output a merge readiness checklist.

1|Updated Dec 9, 2024
One-click install
npx skills add https://github.com/hadenlabs/tasks --skill github-validate-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-validate-pr
Source: https://github.com/hadenlabs/tasks/tree/main/.claude/skills/github-validate-pr
Command: npx skills add https://github.com/hadenlabs/tasks --skill github-validate-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies checks, blockers, and security signals in a pull request and provides actionable remediation steps.

Core Features & Use Cases

  • Ask which PR to validate: prompts for the PR to review (number or URL).
  • List PRs assigned to you: surfaces your open PRs for quick selection.
  • Inspect CI failures, required checks, and merge blockers: analyzes status, failures, and merge readiness.
  • Look for security signals: detects potential vulnerabilities or dependency issues when available.
  • Produce an actionable checklist: delivers concrete next steps to get the PR merge-ready.

Quick Start

Ask which PR to validate by providing its number or URL to trigger a validation workflow.

Frequently Asked Questions about github-validate-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if a GitHub pull request is ready to merge?

To check if a GitHub pull request is ready to merge, you need to analyze CI checks, required statuses, and merge blockers. This Skill reads PR metadata via the GitHub API to surface these issues and provides an actionable checklist for merge readiness.

How do I find CI failures and merge blockers in a GitHub PR?

You can find CI failures and merge blockers in a GitHub PR by inspecting the PR status and required checks. The validation workflow reads PR metadata to detect failed statuses and outputs a structured plan with concrete next steps to resolve them.

Can I list my assigned GitHub pull requests for quick validation?

Yes, you can list your assigned GitHub pull requests for quick validation. The Skill surfaces your open PRs for easy selection, allowing you to choose a specific PR by number or URL to trigger the validation and security signal analysis workflow.

Does validating a GitHub PR require GitHub authentication context?

Yes, validating a GitHub PR requires GitHub authentication context. The Skill reads PR metadata via the gh command line tool or GitHub API to inspect CI failures and security signals, meaning valid authentication is necessary to access the repository data.

What are the limitations of automated PR validation for security signals?

A limitation of automated PR validation is that it only detects potential security signals and dependency issues when available in the PR metadata. It surfaces these vulnerabilities alongside CI failures but does not perform deep, static code analysis beyond the data provided by the GitHub API.