prb

Synchronize local branches with trunk, enforce review gates, and manage database migrations.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/davidsolheim/skills --skill prb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prb
Source: https://github.com/davidsolheim/skills/tree/main/prb
Command: npx skills add https://github.com/davidsolheim/skills --skill prb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill automates the complex, multi-step process of shipping code, ensuring that local development branches are always synced with the trunk, reviewed, and safely merged without manual oversight.

Core Features & Use Cases

  • Local Code Review Gate: Automatically enforces code review rules and creates Linear tickets for actionable findings before any code is pushed.
  • Closed-Loop Delivery: Manages the entire lifecycle from merging the latest trunk into your dev branch to babysitting CI/CD pipelines and performing production database migrations.
  • Use Case: Use this when you have finished a feature on a local dev branch and want to ensure it is reviewed, tested, and merged into main without manually checking for conflicts, CI failures, or pending database schema updates.

Quick Start

Run the prb skill to push your current session work to the dev branch and initiate the automated review and merge process.

Frequently Asked Questions about prb

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

FAQPage Schema
How do I automate code review and merge dev branches into the main trunk?

Automated code review and merging is handled by enforcing review gates and syncing local development branches with the remote trunk. This ensures code is reviewed and safely merged without manual oversight or conflict checks.

Can I automate Linear ticket integration with my CI/CD pipeline?

Yes, you can automate Linear ticket integration within your CI/CD pipeline. The process creates Linear tickets for actionable code review findings and manages the closed-loop delivery from local branch to production.

How do I safely run production database migrations before merging code?

Production database migrations are safely managed by performing pre-merge production schema validation. This ensures database schema updates are tested and applied automatically during the continuous delivery lifecycle.

What is the best way to monitor CI/CD pipelines automatically after pushing code?

Monitoring CI/CD pipelines automatically is achieved through a closed-loop delivery system that babysits pipelines after code is pushed. It watches for failures and manages the entire lifecycle until code is successfully promoted to production.

Does this automated delivery loop work for full-stack engineering workflows?

Yes, this automated delivery loop applies to professional full-stack engineering workflows. It requires atomic Linear ticket integration and manages complex production schema validation for safe, repeatable code promotion.

Why do I need to sync local development branches with the remote trunk?

Syncing local development branches with the remote trunk is required to ensure branches are always up to date before merging. This prevents merge conflicts and guarantees the automated review loop validates the latest codebase changes.