skills.rest
zmerlynn
zmerlynnCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pr

Rebase, build, lint, test, and open a pull request against main.

19|5|Updated Apr 8, 2026
Search Tags:#automation#git#code-review#preflight#pull-request#build-test#pr-flow
One-click install
npx skills add https://github.com/zmerlynn/manifold-csg --skill pr-zmerlynn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/zmerlynn/manifold-csg/tree/main/.claude/skills/pr
Command: npx skills add https://github.com/zmerlynn/manifold-csg --skill pr-zmerlynn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Branch hygiene is hard to enforce manually; this Skill ensures pre-flight checks are completed before pushing and opening a PR, reducing merge conflicts and rework.

Core Features & Use Cases

  • Pre-flight hygiene checks: rebase on the latest main, build with nalgebra features, run clippy with warnings denied, and execute tests to validate changes.
  • Automated PR creation: opens a pull request against the main branch with a clear, work-in-progress aware title.
  • Use Case: For teams practicing strict code-quality gates before integration, this Skill guarantees a consistent PR workflow across branches.

Quick Start

Push the current branch to origin and open a PR after completing the pre-flight checks.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate pre-flight checks before opening a pull request?▼

Automated pre-flight checks before opening a pull request are handled by running git fetch, rebasing on origin/main, building, linting, and testing before pushing your branch and creating the PR. This enforces branch hygiene and reduces merge conflicts.

What is the best way to enforce branch hygiene before pushing a Git branch?▼

Enforcing branch hygiene before pushing a Git branch requires a consistent pre-flight sequence: rebasing on the latest main, running builds, executing clippy with warnings denied, and testing. Automating this workflow guarantees code-quality gates are met before integration.

Can I use this automated PR workflow with Rust and Cargo feature flags?▼

Yes, the automated PR workflow supports Rust and Cargo feature flags by explicitly running cargo build and cargo test with the nalgebra features flag, while cargo clippy also includes the feature to ensure full compilation and linting coverage.

How does a pre-flight PR flow handle clippy warnings?▼

A pre-flight PR flow handles clippy warnings by running cargo clippy on all targets with the nalgebra feature and denying all warnings. This strict linting gate ensures no new code quality issues are introduced before the branch is pushed.

What steps are required to rebase and push a branch for a code review?▼

Rebasing and pushing a branch for code review requires fetching the latest changes, rebasing onto origin/main, validating the build and tests, reviewing the diff against main, and finally pushing to origin to open a pull request.

Related Skills

Explore More Software Engineering Skills→
adamfilliadamfilli
11

rebase

Rebase the current Git branch onto the latest origin/main branch.

Community
Intermediate
cookeyholdercookeyholder

squash-pr

Squash and merge a GitHub pull request into main after validating review feedback.

Community
Advanced
robertbr123robertbr123

requesting-code-review

Automate code review with security scans, quality checks, and automated fixes.

Community
Advanced
SteveGJonesSteveGJones
41

pr

Create pull requests after pre-push validation and test count verification.

Community
Intermediate