pr-open

Automate pre-PR workflows for the bklit-ui monorepo with validation and structured GitHub pull requests.

1.5k|89|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/bklit/bklit-ui --skill pr-open-bklit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-open
Source: https://github.com/bklit/bklit-ui/tree/main/.agents/skills/pr-open
Command: npx skills add https://github.com/bklit/bklit-ui --skill pr-open-bklit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually running pre-PR checks for the bklit-ui monorepo is time-consuming and error-prone, with easy-to-miss steps like registry rebuilds and lint validation that often lead to broken pull requests requiring rework.

Core Features & Use Cases

  • End-to-end PR automation: Handles staging changes, running pre-commit hooks (including ultracite linting), rebuilding the shadcn UI registry, running production builds, and creating structured GitHub PRs with required test plans.
  • Safety guardrails: Enforces rules like no unrequested force pushes, no skipped hooks, and no secret commits to prevent accidental repository damage.
  • Use case: bklit-ui contributors can run a single workflow to go from local code changes to an open, merge-ready PR without manually tracking validation steps or forgetting required checks.

Quick Start

Use the pr-open skill to commit your recent bklit-ui code changes and open a merge-ready pull request with all required pre-checks completed.

Frequently Asked Questions about pr-open

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

FAQPage Schema
How do I automate pre-commit hooks and linting before opening a pull request?

Automating pre-commit hooks and linting before opening a pull request is handled by running a single workflow that stages changes, enforces ultracite linting compliance, and validates builds. This eliminates manually tracking validation steps and prevents broken PRs.

Why does my shadcn UI registry build break after submitting a pull request?

Your shadcn UI registry build breaks when artifact synchronization is missed during manual PR preparation. Automating the pre-PR workflow rebuilds the registry artifacts and validates production builds before submission, ensuring the pull request remains merge-ready.

What is the best way to standardize GitHub pull request documentation with a test plan?

Standardizing GitHub pull request documentation with a test plan requires a workflow that generates structured PRs containing required test plan checklists. This automation enforces documentation compliance alongside pre-commit hook and lint validation for every contribution.

Can I force push or skip hooks when staging code changes in a monorepo?

You cannot force push unrequested changes or skip pre-commit hooks in this workflow. Safety guardrails explicitly prevent unrequested force pushes, skipped hooks, and secret commits to protect the repository from accidental damage during PR automation.

Does the pre-PR workflow support monorepo contributors working with bklit-ui?

The pre-PR workflow fully supports bklit-ui monorepo contributors. It is designed for developers staging code changes, running pre-commit hooks, rebuilding the shadcn UI registry, and validating production builds before opening a structured GitHub pull request.