skills.rest
SnowboardTechie
SnowboardTechieCOMMUNITY
Explore all skills by this author →
GitHub

catalog-review

Review catalog PRs for downstream impact on TypeSpec and vitest packages.

Updated Oct 28, 2025
Search Tags:#validation#dependencies#catalog#pnpm#review#pull-request#downstream-impact
One-click install
npx skills add https://github.com/SnowboardTechie/dotfiles --skill catalog-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: catalog-review
Source: https://github.com/SnowboardTechie/dotfiles/tree/main/dot-config/opencode/skills/catalog-review
Command: npx skills add https://github.com/SnowboardTechie/dotfiles --skill catalog-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Catalog PRs often affect multiple packages and downstream consumers; this skill provides a structured review process to assess downstream impact and validation results.

Core Features & Use Cases

  • Confirm a PR is catalog-managed and identify changes to pnpm-workspace.yaml, pnpm-lock.yaml, or catalog-managed packages.
  • Assess downstream impact across TypeSpec packages, tooling, and website.
  • Validate results against the catalog validation workflow, audit steps, and CI signals to determine merge readiness.
  • Provide actionable recommendations and proper documentation when merging.

Quick Start

Review the latest catalog PR and follow the outlined steps to assess impact, validation, and merge readiness.

Frequently Asked Questions about catalog-review

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

FAQPage Schema
How do I review a catalog PR for downstream impact on dependent packages?▼

To assess downstream impact, identify changes in pnpm-workspace.yaml or pnpm-lock.yaml, then evaluate how those modifications affect dependent packages like TypeSpec and vitest before deciding mergeability.

What validation steps are needed to determine catalog PR mergeability?▼

Determining catalog PR mergeability requires running the catalog validation workflow, auditing results, checking core CI, and verifying downstream project CI signals to produce a clear merge decision with rationale.

How does pnpm catalog management affect downstream project CI?▼

pnpm catalog management affects downstream project CI by propagating dependency changes to consumers like TypeSpec and website tooling, requiring validation workflows and CI checks to confirm no breaking downstream impact before merging.

Can I automate pull request reviews for pnpm catalog-managed packages?▼

Yes, you can automate pull request reviews for pnpm catalog-managed packages by applying a structured validation path that checks catalog changes, audits results, and evaluates downstream CI signals to output merge recommendations.

What should I do when a catalog validation workflow fails on a downstream package?▼

When a catalog validation workflow fails on a downstream package, you should hold the merge, review the audit results and CI failures, and apply required follow-up fixes before reassessing the pull request mergeability.

Related Skills

Explore More Software Engineering Skills→
octoploreroctoplorer
5

pnpm

Manage JavaScript dependencies with pnpm workspaces and lockfiles.

Official
Advanced
DGouronDGouron
41

review-followup-example

Verify review comments are addressed in new commits and generate follow-up reports.

Community
Intermediate
louisbrulenaudetlouisbrulenaudet
18

pnpm

Manage pnpm workspace dependencies, catalogs, and Turborepo tasks in monorepos.

Community
Advanced
gerald-icagerald-ica

gitnexus-pr-review

Map pull request changes to execution flows and assess merge risk.

Community
Advanced