green

Verify typecheck, build, test, and format across repository workspaces.

2|Updated Mar 15, 2024
One-click install
npx skills add https://github.com/finlaysonstudio/jaypie --skill green
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: green
Source: https://github.com/finlaysonstudio/jaypie/tree/main/.claude/skills/green
Command: npx skills add https://github.com/finlaysonstudio/jaypie --skill green

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Completion criteria -- typecheck, build, test, format must all pass to ensure a healthy, deployable codebase.

Core Features & Use Cases

  • Enforces a four-criteria health gate: typecheck, build, test, and format across packages.
  • Ideal for CI pipelines and local development to guarantee green status before merges or releases.
  • Useful for auditing project health and quickly pinpointing failing steps in a multi-package workspace.

Quick Start

Run the four checks locally: typecheck, build, test, and format for all affected packages to verify a green state.

Frequently Asked Questions about green

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

FAQPage Schema
How do I verify that my multi-package workspace passes typecheck, build, test, and format checks?

To verify a multi-package workspace, run all four criteria checks locally to determine overall health status under CI-like conditions, reporting success or detailed failure summaries with required fixes.

What is the best way to enforce a green build status across multiple packages before merging?

The best way to enforce a green build status is applying a four-criteria health gate across all affected packages, verifying typecheck, build, test, and format pass before merges or releases.

Why does my CI pipeline fail to catch formatting and typecheck errors across different workspaces?

Your CI pipeline may fail to catch errors if it does not apply a unified health gate verifying typecheck, build, test, and format across all affected packages to determine overall status.

How do I identify which specific workspace package is failing typecheck, build, test, or format?

To identify the failing package, run the four checks across all workspaces to pinpoint failing steps and generate a detailed summary of required fixes for the affected packages.

Do I need to run typecheck, build, test, and format separately to determine overall codebase health?

No, you do not need to run them separately; you can apply the checks to multiple packages and workspaces simultaneously to determine overall health status and report success or failures.