package-review

Validates GitHub packages by testing documentation links and composer.json quality.

5|Updated Aug 22, 2025

Search Tags:#validation #GitHub #quality-check #open-source #documentation-links #package-review #composer.json

Ready to run

npx skills add https://github.com/pekral/cursor-rules --skill package-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: package-review
Source: https://github.com/pekral/cursor-rules/tree/main/skills/package-review
Command: npx skills add https://github.com/pekral/cursor-rules --skill package-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Package Review provides automated validation for public GitHub packages by testing documentation links and ensuring composer.json quality, reducing manual QA effort.

Core Features & Use Cases

Validate documentation links across repositories and surface broken URLs.
Assess composer.json quality, including required fields and meaningful values.
Use Case: You want to verify a new public package's health before recommending it in a guide.

Quick Start

Use the package-review skill to scan a public repository, then review the generated checklist and remediation notes.

Frequently Asked Questions about package-review

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

FAQPage Schema

How do I validate documentation links in a public GitHub repository?▼

To validate documentation links in a public GitHub repository, you can scan it to automatically test URLs and surface broken links. This process reduces manual QA effort by verifying documentation integrity across open-source packages.

How do I check if my composer.json has the required fields and valid values?▼

To check if your composer.json has the required fields and valid values, you can run an automated quality assessment. This enforces checks for required composer.json keys, validates their values, and ensures overall package metadata correctness.

What is the best way to assess the health of an open-source package before recommending it?▼

The best way to assess the health of an open-source package before recommending it is to run an automated validation scan. This tests documentation links and verifies composer.json quality to generate a structured remediation checklist.

Can I use this validation process for private repositories?▼

This validation process is designed for public GitHub packages and open-source projects. The metadata does not indicate support for private repositories, focusing its quality checks and link validation specifically on public package health.

What do I need to scan a public repository for package health and metadata correctness?▼

To scan a public repository for package health and metadata correctness, you need the public GitHub package URL. The process then tests documentation links, checks composer.json required keys, and outputs a structured remediation checklist.