markdowntown-monorepo
Monorepo workflow for coordinating CLI + web changes, tests, and docs in markdowntown.
When & Why to Use This Skill
The markdowntown-monorepo skill provides a specialized workflow for managing and coordinating changes within a complex monorepo environment. It streamlines the development process by integrating CLI and web application updates, automating testing and linting procedures, and ensuring documentation consistency across the project. By utilizing standardized commands and prompt templates, it enhances developer productivity and maintains high code quality standards.
Use Cases
- Coordinating Cross-Component Updates: Seamlessly manage features that require simultaneous changes to the CLI tool and the web interface, ensuring all parts are tested and linted correctly.
- Automated Quality Assurance: Execute specific testing suites, such as unit tests for web apps and CLI-specific linting, to maintain codebase stability during rapid development.
- Documentation Synchronization: Streamline the process of updating technical documentation by enforcing markdown linting and maintaining canonical links between CLI specifications and web-based docs.
- Workflow Standardization: Use pre-defined prompt templates and root-level guidelines to ensure all contributors follow the same repo-wide expectations for testing and deployment.
| name | markdowntown-monorepo |
|---|---|
| description | Monorepo workflow for coordinating CLI + web changes, tests, and docs in markdowntown. |
markdowntown-monorepo
- Follow root
AGENTS.mdfor repo-wide workflow and test expectations. - For CLI changes:
cd cli && make lintandcd cli && make test. - For web changes:
pnpm -C apps/web lint,pnpm -C apps/web compile,pnpm -C apps/web test:unit. - For docs-only changes:
pnpm -C apps/web lint:mdandcd cli && make lintif CLI docs change. - Keep CLI scan/audit specs canonical under
cli/docs/and link from web docs. - Use prompt templates in
codex/prompts/for common scan/test flows.