skills.rest
bibektimilsina00
bibektimilsina00COMMUNITY
Explore all skills by this author →
GitHub

ship

Run lint and TypeScript checks, commit, push, and open a GitHub pull request.

1|1|Updated May 13, 2026
Search Tags:#git#pull request#conventional commits#lint#CI readiness#repository workflow#typescript tsc
One-click install
npx skills add https://github.com/bibektimilsina00/fuse_monorepo --skill ship-bibektimilsina00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/bibektimilsina00/fuse_monorepo/tree/main/.agents/skills/ship
Command: npx skills add https://github.com/bibektimilsina00/fuse_monorepo --skill ship-bibektimilsina00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you safely deliver code changes by automating the repetitive steps of checking status, running lint and type checks, committing with a consistent message, pushing, and opening a pull request.

Core Features & Use Cases

  • Pre-ship verification: Runs make lint (ruff + eslint) and a TypeScript no-emit type check from apps/web/ to catch issues early.
  • Conventional Commits messaging: Generates a properly formatted commit message so history stays clean and searchable.
  • End-to-end delivery workflow: Stages, commits, pushes to the current branch, and creates a PR with a structured description and checklist.

Quick Start

Run the ship command to commit your current changes, push them to the origin branch, and open a PR after linting and type-checking pass.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate lint checks and conventional commits before opening a pull request?▼

To automate lint checks before a pull request, you can run pre-ship verification commands like make lint and tsc --noEmit. This workflow stages changes, generates a conventional commit message, pushes the branch, and uses gh pr create to open a GitHub pull request with a structured body.

What is the best way to enforce conventional commit messages in a mixed Python and TypeScript codebase?▼

Enforcing conventional commit messages in a mixed Python and TypeScript codebase requires a deterministic pre-commit workflow. This process generates properly formatted conventional commit messages after successfully validating the codebase with ruff, eslint, and tsc type checks.

Can I use this workflow to run TypeScript type checks and push changes to GitHub?▼

Yes, you can use this workflow to run TypeScript type checks and push changes to GitHub. It executes tsc with the --noEmit flag from the apps/web/ directory, stages and commits validated changes, pushes them to the origin branch, and opens a pull request using gh pr create.

Does this repository workflow require the GitHub CLI to create pull requests?▼

Yes, this repository workflow requires the GitHub CLI to create pull requests. The process explicitly uses the gh pr create command with a structured title and PR body to open the pull request after successfully pushing the committed branch to the origin.

Why would pre-ship CI readiness checks fail when using make lint?▼

Pre-ship CI readiness checks fail when using make lint if ruff or eslint detects code quality issues. The workflow halts the commit, push, and pull request creation process until these linting and TypeScript no-emit type check errors are fully resolved.

Related Skills

Explore More Software Engineering Skills→
Thawatchai-PetkaewThawatchai-Petkaew

open-pr

Create a branch, commit with Conventional Commits, and open a pull request to staging.

Community
Intermediate
Renzo-TognellaRenzo-Tognella

yeet

Automate GitHub pull request creation using the GitHub CLI.

Community
Intermediate
bennybennisonbennybennison

verification-loop

Run sequential build, type, lint, test, security, and diff checks.

Community
Intermediate
0tarof0tarof

create-pr

Automate GitHub pull request creation with Bash, Git, and gh.

Community
Intermediate