Agent skill

Monorepo Delivery

by shepherdjerred in shepherdjerred/monorepo

Deliver changes in this monorepo through Git-Spice, focused checks, Woodpecker CI, automated review, and PR evidence.

GPL-3.0Auto-check passedDevelopment

Install Monorepo Delivery

skills CLI
$ npx skills add shepherdjerred/monorepo --skill monorepo-delivery -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install shepherdjerred/monorepo monorepo-delivery --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/shepherdjerred/monorepo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/monorepo-delivery .claude/skills/monorepo-delivery && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
monorepo-delivery
GitHub stars
112
Token cost
~962 tokens
SKILL.md length
516 words
Files
1
Skills in repo
63
Repo updated
First seen
Licence
GPL-3.0

At a glance

Deliver changes in this monorepo through Git-Spice, focused checks, Woodpecker CI, automated review, and PR evidence.

  • Works in 6 steps: Inspect the current branch, worktree,… → Run focused package tasks with Turbo… → For a browser-visible change, render it… → …
  • Review findings
  • SKILL.md covers Work locally and Prove readiness
  • Calls gh and bunx

What it does

Monorepo Delivery is an agent skill from shepherdjerred/monorepo. Deliver changes in this monorepo through Git-Spice, focused checks, Woodpecker CI, automated review, and PR evidence. Use for branches, commits, PRs, CI failures, review findings, or release-readiness claims.

Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Monorepo tooling, Failing and flaky tests and Code review. It works with Git. The repository describes itself as: Monorepo for all of my projects. The licence is GPL-3.0.

When your agent uses it

  • Review findings
  • Release-readiness claims

Example prompts

  • “/monorepo-delivery”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Inspect the current branch, worktree, and complete base diff. Preserve
  2. Run focused package tasks with Turbo while iterating.
  3. For a browser-visible change, render it with PinchTab and capture the proof
  4. Stage exact paths and run bunx lefthook run pre-commit.
  5. Commit as type(scope): outcome. The primary commit body has Why, What,
  6. Inspect the complete branch diff before submission.

What it can do on your machine

Read from SKILL.md and the folder at commit d66c497. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • bunx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and bunx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Monorepo Delivery loads about 962 tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 516 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~962

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from shepherdjerred/monorepo at commit d66c497, republished under its GPL-3.0 licence (© shepherdjerred). 516 words, ~962 tokens.

Download SKILL.mdSave it as .claude/skills/monorepo-delivery/SKILL.md (or your agent's skills folder).
name
monorepo-delivery
description
Deliver changes in this monorepo through Git-Spice, focused checks, Woodpecker CI, automated review, and PR evidence. Use for branches, commits, PRs, CI failures, review findings, or release-readiness claims.

Monorepo delivery

Use toolkit git-spice for every feature branch and PR operation. A single PR is a stack of one. Never use gs from non-interactive shells, hand-roll a stack rebase, or create a feature PR with gh pr create.

Work locally

  1. Inspect the current branch, worktree, and complete base diff. Preserve unrelated edits.
  2. Run focused package tasks with Turbo while iterating.
  3. For a browser-visible change, render it with PinchTab and capture the proof now, not after review: pinchtab screenshot -o <file> for a state, pinchtab record for a flow. Other user-visible surfaces use their own tool — a rendered asset, a Discord acceptance message, terminal output.
  4. Stage exact paths and run bunx lefthook run pre-commit.
  5. Commit as type(scope): outcome. The primary commit body has Why, What, and Verification.
  6. Inspect the complete branch diff before submission.

Create or update the PR explicitly:

bash
toolkit git-spice branch submit --draft --dry-run --title "type(scope): outcome" --body "..."
toolkit git-spice branch submit --draft --title "type(scope): outcome" --body "..."
toolkit git-spice stack submit --update-only

Use a draft once the branch has a coherent first commit. Draft pushes run the bounded preflight. When the change and focused checks are ready, trigger full verification without another commit:

bash
toolkit git-spice branch submit --no-draft
toolkit ci wait --json

A green draft preflight is not merge evidence. Wait for full verification of the current head after marking it ready. Keep the final body based on the whole branch, not the latest commit.

Prove readiness

  • Woodpecker is authoritative for CI. Use toolkit ci wait <PR> --json for merge readiness and toolkit ci explain <PR> for bounded failure evidence. Keep awaiting the same foreground process. Long queues and builds are normal; elapsed time alone is not a failure. Use toolkit ci load for capacity.
  • Wait exits distinguish CI failure (1), errors (2), human intervention (3), head changes (4), red main (5), timeout (6), and closed/merged PRs (7). On red main, report the failure and await instructions; do not repair main. A timeout is not CI failure. A changed head requires an explicit new wait. Use --until settled when collecting all blocking results is useful. Full command and credential details live in packages/toolkit/README.md.
  • Use toolkit pr review list <PR> --json for authors, priority, full feedback, and raw GitHub API commands. Do not infer CI status from GitHub Actions.
  • Verify the exact PR head. A prior build or a green sibling branch is not evidence for the current commit.
  • Source, CI, artifact publication, ArgoCD deployment, and live behavior are separate claims. Report each independently.
  • Before pushing a review fix, list the finding and resolve or dismiss its thread with a specific audited reason when justified.
  • Never change a real gate, skip a test, or suppress an error merely to make a PR green.
Show full SKILL.md (89 more words)Show less

Attach the proof captured in step 3 with toolkit pr asset <PR> <path> --profile seaweedfs --markdown. A change with a visual or interactive surface reaches review with that artifact; "the diff is small" is not a reason to omit it. Pure logic and internal refactors give exact commands instead. State unperformed live or production checks in the PR body.

Complex work may use several commits inside this one branch. Use multiple stacked PRs only when each branch is independently landable and the requested scope permits more than one PR.

© shepherdjerred, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/monorepo-delivery of shepherdjerred/monorepo.

Open the folder on GitHubat commit d66c497

Compare with similar skills

Monorepo Delivery next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Monorepo Delivery compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Monorepo Delivery this skillshepherdjerred/monorepo112—~962Automated safety check: PassGPL-3.0
Tbdjlevy/strif131—~3.5kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k4 repos~1.1kAutomated safety check: PassMIT
Migrate Internal Package into GhostTryGhost/Ghost56k—~3.8kAutomated safety check: PassMIT
Open Code Review CLIalibaba/open-code-review46k—~3.1kAutomated safety check: PassApache-2.0

Similar skills

  • Tbd

    jlevy/strif

    Git-native issue tracking (beads), coding guidelines, knowledge injection, and spec-driven planning for AI agents.

    131 GitHub stars~3.5k tokensUpdated 4 mo ago
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 4 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.

    56k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Open Code Review CLI

    alibaba/open-code-review

    Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.

    46k GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub stars~1.4k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from shepherdjerred/monorepo

All 63 skills in this repo
  • Bun Runtime Best Practices

    shepherdjerred/monorepo

    Bun runtime APIs and current operational patterns for files, processes, modules, networking, databases, tests, and deployment.

    112 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Bun Test Patterns

    shepherdjerred/monorepo

    Current Bun test runner guidance for discovery, isolation, parallelism, sharding, changed tests, mocks, timers, snapshots, coverage, DOM Testing Library, and integration teardown.

    112 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Bun Workspaces

    shepherdjerred/monorepo

    Current Bun workspace guidance for isolated and hoisted linkers, catalogs, filters, scripts, dependency classes, lockfiles, lifecycle trust, caches, publishing, TypeScript package exports, and…

    112 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Deep Research

    shepherdjerred/monorepo

    This skill should be used when the user asks to "deep research", "research this topic", "investigate thoroughly", "do a deep dive on", "comprehensive research on", "find everything about", "survey…

    112 GitHub stars~4.7k tokensUpdated today
    Auto-check: notes
  • Figma Use

    shepherdjerred/monorepo

    This skill should be used when the user asks to "create a Figma design", "design in Figma", "make a Figma mockup", "create an app icon", "design UI", "render JSX to Figma", "export from Figma"…

    112 GitHub stars~946 tokensUpdated today
    Auto-check passed
  • Fish Helper

    shepherdjerred/monorepo

    Current Fish shell scripting, functions, abbreviations, completions, variables, events, configuration, plugins, testing, and safety guidance.

    112 GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Monorepo Delivery

What does Monorepo Delivery do?

Deliver changes in this monorepo through Git-Spice, focused checks, Woodpecker CI, automated review, and PR evidence. Monorepo Delivery is an agent skill from shepherdjerred/monorepo. Deliver changes in this monorepo through Git-Spice, focused checks, Woodpecker CI, automated review, and PR evidence.

When should I use Monorepo Delivery?

Monorepo Delivery fits situations like: review findings; release-readiness claims.

How do I install Monorepo Delivery in Claude Code?

Run `npx skills add shepherdjerred/monorepo --skill monorepo-delivery -a claude-code`. Or copy the skill folder (.agents/skills/monorepo-delivery in shepherdjerred/monorepo) into .claude/skills/monorepo-delivery in your project. Claude Code loads it when a task matches its description.

How do I install Monorepo Delivery in Codex?

Run `npx skills add shepherdjerred/monorepo --skill monorepo-delivery -a codex`. Or copy the skill folder (.agents/skills/monorepo-delivery in shepherdjerred/monorepo) into .agents/skills/monorepo-delivery in your project. Codex loads it when a task matches its description.

Can I use Monorepo Delivery in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add shepherdjerred/monorepo --skill monorepo-delivery -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/monorepo-delivery, .gemini/skills/monorepo-delivery, .github/skills/monorepo-delivery and .opencode/skills/monorepo-delivery in your project.

What does Monorepo Delivery need to run?

Going by SKILL.md and its folder, Monorepo Delivery needs the command-line tools its instructions call (gh and bunx).

Does Monorepo Delivery access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Monorepo Delivery safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Monorepo Delivery use?

Monorepo Delivery is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Monorepo Delivery use?

About 962 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Monorepo Delivery?

Skills that share tags, products or a category with Monorepo Delivery: Tbd (jlevy/strif, 131 stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars) and Migrate Internal Package into Ghost (TryGhost/Ghost, 56k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Monorepo Delivery?

shepherdjerred (a GitHub user) maintains it in shepherdjerred/monorepo, which has 112 GitHub stars. The repository holds 63 skills in this directory. The repository was last updated on October 10, 2026.

Source: shepherdjerred/monorepo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.