markdowntown-monorepo

Coordinate CLI and web monorepo linting, testing, and documentation updates.

Updated Dec 31, 2025
One-click install
npx skills add https://github.com/joelklabo/markdowntown-cli --skill markdowntown-monorepo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: markdowntown-monorepo
Source: https://github.com/joelklabo/markdowntown-cli/tree/main/codex/skills/markdowntown-monorepo
Command: npx skills add https://github.com/joelklabo/markdowntown-cli --skill markdowntown-monorepo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures consistent, repeatable workflows for a monorepo that contains both a CLI and a web app by defining how to lint, test, and update documentation so changes do not break other parts of the repository.

Core Features & Use Cases

  • Unified Workflow Guidance: Clear steps for CLI and web changes, including linting and testing commands for each project area.
  • Docs and Specs Management: Guidance to keep CLI scan/audit specs canonical under cli/docs and link to web docs to avoid divergence.
  • Developer Efficiency: Use of prompt templates and AGENTS.md to standardize handoffs, Workbench snapshots, and export/patch flows for reviews and syncs.
  • Use Case: A contributor updates a CLI command and related web UI; follow the checklist to run CLI lint/tests, run web lint/compile/unit tests, and update linked docs to ensure the snapshot syncs cleanly.

Quick Start

Coordinate a change by running CLI lint and tests, running web lint, compile, and unit tests, and verifying any docs updates per AGENTS.md.

Frequently Asked Questions about markdowntown-monorepo

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

FAQPage Schema
How do I coordinate CLI and web monorepo workflows for consistent testing?

To coordinate monorepo workflows, you run CLI lint and tests, execute web lint, compile, and unit tests, and update linked documentation per AGENTS.md guidelines to ensure changes do not break other repository parts.

What is the best way to manage documentation updates in a CLI and web monorepo?

Managing documentation updates requires keeping CLI scan and audit specs canonical under cli/docs and linking them to web docs to avoid divergence, using prompt templates and AGENTS.md to standardize Workbench handoffs and export flows.

How do I validate CLI builds and run web app tests in a pnpm monorepo?

Validating CLI builds and web app tests involves orchestrating repo-level guides, running project-specific make and pnpm commands for linting and compiling, and following clear verification steps for scans, audits, and Workbench handoffs.

Does this monorepo workflow approach support standardized handoffs for contributors?

Yes, the monorepo workflow supports standardized handoffs by using AGENTS.md and prompt templates to standardize Workbench snapshots, export and patch flows, and review syncs for maintainers and contributors.

Why do I need to run separate lint and test commands for CLI and web projects?

Separate lint and test commands are needed because a monorepo contains distinct CLI and web app areas, requiring specific make and pnpm commands for each project to prevent changes in one from breaking the other.