malfig-ship

Run TypeScript, ESLint, build, and Playwright gates before creating a pull request and merging.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/DaBigHomie/ugwtf --skill malfig-ship
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: malfig-ship
Source: https://github.com/DaBigHomie/ugwtf/tree/main/.cursor/skills/malfig-ship
Command: npx skills add https://github.com/DaBigHomie/ugwtf --skill malfig-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Streamlines the process of taking a branch's work from 'done' to 'merged' through the MALFIG gates, eliminating manual steps and ensuring consistency.

Core Features & Use Cases

  • Automated Gate Checks: Executes gates like TypeScript compilation, ESLint, build, and Playwright test automatically.
  • Commit Management: Commits with MALFIG-compliant messages and ensures all gates pass before committing.
  • PR Creation & Merge: Opens a PR with the branch, waits for CI/Vercel green, then squash-merges.
  • Use Case: Ideal for teams using MALFIG for CI/CD and needing an automated way to ship features through the gates without manual intervention.

Quick Start

Use the malfig-ship skill to initiate the shipping process for your feature branch.

Frequently Asked Questions about malfig-ship

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

FAQPage Schema
How do I automate feature shipping and PR creation with CI/CD gates?

To automate feature shipping, the Skill executes TypeScript, ESLint, build, and Playwright gates sequentially before creating a pull request. It commits with compliant messages, waits for CI/Vercel green status, and then squash-merges the branch automatically.

What is the MALFIG framework for branch management and automated merging?

The MALFIG framework is a CI/CD system that enforces automated gate checks before merging. This Skill operates within it to execute TypeScript, ESLint, build, and Playwright tests, ensuring branch management consistency from completion to squash-merge.

Do I need a local gate system setup to run automated PR creation and merge checks?

Yes, you need a local gate system setup and access to the repository's commit history. These prerequisites allow the Skill to execute the MALFIG gates locally and validate all checks before opening a pull request and merging.

Can I use this to run TypeScript and Playwright checks before opening a pull request?

Yes, you can run TypeScript and Playwright checks before opening a pull request. The Skill executes these automated gates alongside ESLint and build processes to ensure all validations pass before committing and creating the PR.

How does automated squash-merging work after CI and Vercel checks pass?

Automated squash-merging occurs after the Skill creates a pull request and waits for CI and Vercel checks to turn green. Once all MALFIG gates and remote validations pass, it automatically squash-merges the feature branch into the target branch.

Why does my feature branch fail to commit before PR creation during automated shipping?

Your feature branch fails to commit if any MALFIG gate, such as TypeScript compilation, ESLint, build, or Playwright tests, fails validation. The Skill ensures all gates pass before committing with MALFIG-compliant messages and proceeding to PR creation.