skills.rest
nanokajs
nanokajsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

ship-pr

Run format, lint, typecheck, and test checks before creating a pull request.

Updated May 2, 2026
Search Tags:#code quality#GitHub#PR preparation#PR validation#CI pipeline
One-click install
npx skills add https://github.com/nanokajs/nanoka --skill ship-pr-nanokajs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship-pr
Source: https://github.com/nanokajs/nanoka/tree/main/.claude/skills/ship-pr
Command: npx skills add https://github.com/nanokajs/nanoka --skill ship-pr-nanokajs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pnpm, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the preparation process for creating Pull Requests (PRs) by automating format, lint, typecheck, and test validations. It ensures that only PRs that pass all checks are created, reducing errors and improving code quality.

Core Features & Use Cases

  • Automated Checks: Run format, lint, typecheck, and test validations in a single step.
  • Error Handling: Stops the process if any check fails, preventing the creation of flawed PRs.
  • Efficiency: Saves time by automating the preparation steps for PRs.

Quick Start

Run the ship-pr skill to validate and create a PR before submitting your changes.

Frequently Asked Questions about ship-pr

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

FAQPage Schema
How do I automate Pull Request preparation with format, lint, typecheck, and test validation?▼

Automate Pull Request preparation by running format, lint, typecheck, and test validations in a single pipeline step. This ensures code quality and consistency before committing changes to a repository, stopping the process if any check fails.

Do I need pnpm to automate PR validation checks?▼

Yes, you need pnpm installed to execute the automated PR validation pipeline. The validation process requires pnpm for running the format, lint, typecheck, and test checks before creating a Pull Request.

What's the best way to prevent creating flawed Pull Requests with failing checks?▼

The best way to prevent flawed Pull Requests is to use an automated validation pipeline that stops the process if any format, lint, typecheck, or test check fails, ensuring only passing PRs are created.

Can I use GitHub MCP server for PR creation after running code quality checks?▼

Yes, the GitHub MCP server is required for PR creation. The pipeline runs code quality validations first, and only creates the Pull Request via the GitHub MCP server if all checks pass successfully.

Why does my CI pipeline PR validation stop before creating a Pull Request?▼

Your PR validation stops because the automated pipeline encounters a failing format, lint, typecheck, or test check. This error handling mechanism prevents the creation of flawed Pull Requests with code quality issues.

What is automated PR preparation and when do I need it in my CI pipeline?▼

Automated PR preparation is the process of running format, lint, typecheck, and test validations before submitting changes. You need it in your CI pipeline to ensure code quality and consistency before committing changes to a repository.

Related Skills

Explore More Software Engineering Skills→
bigbiobigbio
11

sdrf:setup

Install and configure SDRF annotation dependencies via Conda, Pip, or uv.

Official
Intermediate
ibalasiteibalasite

land-and-deploy

Merge pull requests, wait for CI, and verify production health via canary checks.

Community
Advanced
TheGreatLTheGreatL

fix

Automate code linting and formatting with Prettier and a linter before commits.

Community
Basic
patricio0312revpatricio0312rev
5

quality-gates-enforcer

Enforce CI quality gates for coverage, linting, type checks, and security in Node.js PR workflows.

Community
Advanced