pr-check-deps

Validate GitHub CLI installation, authentication, and extension version prerequisites.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/jeremygiberson/gh-pr-tasks-plugin --skill pr-check-deps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-check-deps
Source: https://github.com/jeremygiberson/gh-pr-tasks-plugin/tree/main/skills/pr-check-deps
Command: npx skills add https://github.com/jeremygiberson/gh-pr-tasks-plugin --skill pr-check-deps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates GitHub CLI prerequisites for PR workflow tasks.

Core Features & Use Cases

  • Environment validation: gh CLI presence, authentication, and required extension installation and version checks.
  • Safe gating: called automatically by other pr-* skills at the start of their workflows, preventing downstream failures due to misconfigurations.
  • Remediation guidance: provides actionable steps to fix missing or outdated components.

Quick Start

Run pr-check-deps at the start of any pr-* workflow to verify gh CLI readiness before proceeding.

Frequently Asked Questions about pr-check-deps

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

FAQPage Schema
How do I validate GitHub CLI prerequisites before running a PR workflow?

You can validate GitHub CLI prerequisites by checking that gh is installed, authenticated, and that the gh-pr-review extension matches the approved pinned version. This ensures your PR workflow environment is fully configured and ready.

Do I need the gh-pr-review extension installed to automate pull request checks?

Yes, automating pull request checks requires the gh-pr-review extension installed at an approved pinned version. The validation process also verifies the extension's release tag integrity to ensure safe gating before PR workflows proceed.

What happens if my gh CLI authentication fails during environment validation for PR tasks?

If gh CLI authentication fails during environment validation, the process halts and provides actionable remediation guidance. This safe gating mechanism prevents misconfigured environments from causing downstream failures in PR-related automation tasks.

How do I check if my GitHub CLI version and extensions are correctly configured for PR automation?

Check your configuration by running a validation step that tests gh CLI version, authentication status, and extension installation. It matches the installed gh-pr-review extension version against the approved release to confirm your environment is ready for PR automation.

Can I use GitHub CLI workflows without verifying my extension release tag integrity?

Using GitHub CLI workflows without verifying extension release tag integrity risks running unapproved or compromised extension versions. Validating the release tag ensures the gh-pr-review extension matches the approved pinned release before executing PR tasks.