skills.rest
pohlai88
pohlai88COMMUNITY
Explore all skills by this author →
GitHub

ship-pr

Runs lint and test gates, then opens a pull request from a branch.

Updated Sep 5, 2026
Search Tags:#code quality#automation#git#testing#pull request#lint#ci
One-click install
npx skills add https://github.com/pohlai88/afenda-xforge-v5 --skill ship-pr-pohlai88
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship-pr
Source: https://github.com/pohlai88/afenda-xforge-v5/tree/main/.agents/skills/pr-to-lint-rule/ship-pr
Command: npx skills add https://github.com/pohlai88/afenda-xforge-v5 --skill ship-pr-pohlai88

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Opening a pull request before checks pass leads to broken builds and wasted review cycles. This Skill enforces a gated pipeline that runs the linter and test suite first, only opening the PR once everything is green. ## Core Features & Use Cases - Gated lint step: Runs npm run lint and blocks progress until it passes. - Gated test step with retries: Runs npm test with up to 3 retries before proceeding. - Automated PR creation: Opens a pull request from a specified branch with an optional title. - Use Case: A developer finishes a feature branch and wants to ship it. Instead of manually running checks and opening the PR, they invoke this Skill with the branch name and let the gates verify quality first. ## Quick Start Run the ship-pr skill with my feature branch 'feature/login-form' and title 'Add login form' to lint, test, and open the pull request.

Frequently Asked Questions about ship-pr

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

FAQPage Schema
How do I open a pull request only after tests pass?▼

Use a gated pipeline that runs npm run lint and npm test before creating the PR. This Skill blocks each step until its gate passes, then opens the pull request from your specified branch.

How to automate lint and test checks before a PR?▼

Define lint and test commands as gates in a skill pipeline. The linter runs first and must pass, then the test suite runs with up to 3 retries, and only then is the pull request opened.

What happens if the test suite keeps failing?▼

The test gate retries npm test up to 3 times. If it still fails after the retries, the pipeline stops and no pull request is opened, so you must fix the failures first.

Can I open a PR without a title using this workflow?▼

Yes, the title argument is optional. Only the branch name is required; if you omit the title, the pull request is opened without a custom title.

Does this work with projects that do not use npm scripts?▼

No, the gates are hardcoded to npm run lint and npm test. Projects using other package managers or check commands would need the gate commands adjusted to match their tooling.

Related Skills

Explore More Software Engineering Skills→
Hey-DigaHey-Diga
16

create-pr

Create a draft pull request after running lint, typecheck, and test scripts.

Official
Advanced
bitpantrybitpantry

finish-pr

Merge reviewed GitHub pull requests after tests pass and branches sync.

Community
Advanced
charchesscharchess
1

vixens-gitops

Manage Vixens GitOps pull requests, production promotion, and branch protection.

Community
Advanced
VilnaCRM-OrgVilnaCRM-Org
1

pr-batch-merge-validation

Validates which queued pull requests can merge together by testing merged trees against CI gates.

Official
Intermediate