pr

Name: pr
Availability: InStock
Author: Kubb

Automate pull request preconditions, changeset usage, and release guidance in a monorepo.

22|3|Updated Sep 12, 2025

Search Tags:#release #lint #code-review #pull-request #typecheck #changeset #pr-checklist

Ready to run

npx skills add https://github.com/kubb-labs/fabric --skill pr-kubb-labs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/kubb-labs/fabric/tree/main/.skills/pr
Command: npx skills add https://github.com/kubb-labs/fabric --skill pr-kubb-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes how teams prepare pull requests by clarifying preconditions, changeset usage, and reviewer expectations, reducing merge conflicts and churn.

Core Features & Use Cases

Enforces the PR checklist: format, lint, typecheck, tests.
Guides changeset creation and version bumps for releases.
Provides a release and documentation update workflow, ensuring consistent changelog updates.

Quick Start

Outline PR preconditions for a new feature in the monorepo and apply the recommended commands to validate formatting, linting, type checks, tests, and changeset creation.

Frequently Asked Questions about pr

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

FAQPage Schema

How do I automate pull request preconditions in a monorepo?▼

Automating pull request preconditions in a monorepo requires enforcing a PR checklist for formatting, linting, typecheck, and tests to reduce merge friction. This standardizes reviewer expectations and changelog updates to reduce merge conflicts.

What is the best way to manage changesets and version bumps for releases?▼

Managing changesets and version bumps for releases is best handled by guiding changeset creation and applying proper version bumps. This ensures consistent changelog updates and standardizes documentation update workflows across the monorepo.

How does a PR checklist reduce merge conflicts and churn?▼

A PR checklist reduces merge conflicts and churn by clarifying preconditions and reviewer expectations before merging. It enforces required checks for format, lint, typecheck, and tests to maintain code quality and consistent changeset usage.

Do I need to run tests and typecheck before creating a pull request?▼

You need to run tests and typecheck before creating a pull request to satisfy required preconditions. Enforcing these checks alongside formatting and linting reduces merge friction and ensures the PR meets reviewer expectations.

Can I standardize documentation update workflows for releases in a monorepo?▼

You can standardize documentation update workflows for releases in a monorepo by integrating changeset usage with version bumps. This provides a consistent release workflow ensuring proper changelog updates and reviewer expectations are met.

What are the limitations of automated release guidance for pull requests?▼

Automated release guidance for pull requests is limited to standardizing preconditions, changeset usage, and reviewer expectations within a monorepo. It focuses on format, lint, typecheck, tests, and version bumps but does not resolve complex merge conflicts directly.