Menu

Individual skill

monorepo-deploy

0upvotes

Deploying services from a monorepo to PaaS — selective builds, shared code, and per-service pipelines.

skills/monorepo-deploy/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
54
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

Monorepos keep related services in one repository — shared types, atomic
cross-service changes, one PR for the whole feature. But PaaS platforms
deploy from repos, and naively that means rebuilding everything on every
commit. This skill covers deploying monorepo services independently:
selective builds, shared packages, and per-service pipelines.

## When to use

- Structuring a monorepo (apps + shared packages) for PaaS deployment
- Setting up per-service build triggers (only build what changed)
- Sharing code between services without publishing packages
- Managing per-service env config within one repo
Back to top