
Bootstrap Monorepo
- 115 installs
- 62 repo stars
- Updated August 3, 2026
- terrylica/cc-skills
Use bootstrap-monorepo for development tasks
About
bootstrap-monorepo: A skill for development. This provides functionality for development workflows.
- bootstrap-monorepo
Bootstrap Monorepo by the numbers
- 115 all-time installs (skills.sh)
- +1 installs in the week ending Jul 27, 2026 (Skillselion tracking)
- Ranked #2,892 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/terrylica/cc-skills --skill bootstrap-monorepoAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 115 |
|---|---|
| repo stars | ★ 62 |
| Last updated | August 3, 2026 |
| Repository | terrylica/cc-skills ↗ |
What it does
Use bootstrap-monorepo for development tasks
Files
Bootstrap Polyglot Monorepo
This skill redirects to the canonical reference in mise-tasks.
→ See: mise-tasks/references/bootstrap-monorepo.md
Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.
When to Use This Skill
Use this skill when:
- Starting a new polyglot monorepo from scratch
- Setting up Python + Rust + Bun/TypeScript project structure
- Need autonomous 9-phase bootstrap workflow (includes release setup)
- Want Pants + mise integration for affected detection
Stack
| Tool | Responsibility |
|---|---|
| mise | Runtime versions (Python, Node, Rust) + environment variables |
| Pants | Build orchestration + native affected detection + dependency inference |
Quick Commands
# After bootstrap, use these Pants commands:
pants --changed-since=origin/main test # Test affected
pants --changed-since=origin/main lint # Lint affected
pants tailor # Generate BUILD files
pants list :: # List all targetsRelated Skills
itp:mise-tasks- Task orchestration and affected detection (Level 11)itp:mise-configuration- Environment and tool version managementitp:semantic-release- Release automation (Phase 8 reference)
---
Troubleshooting
| Issue | Cause | Solution |
|---|---|---|
| Pants not found | Not installed | Install via brew install pantsbuild/tap/pants |
| mise not loading | Shell hook not configured | Configure mise shell hook in ~/.zshrc |
| BUILD files not generated | Missing pants tailor | Run pants tailor to generate BUILD files |
| Affected detection empty | No base branch set | Ensure origin/main exists and is up to date |
| Python version mismatch | mise vs Pants conflict | Align Python version in mise.toml and pants.toml |
| Rust targets not found | Pants Rust backend missing | Enable Rust backend in pants.toml |
| Node/Bun not detected | Not in mise tools | Add to mise.toml: node = "latest" or bun |
| Dependency inference fails | Missing imports in source | Ensure explicit imports, run pants tailor again |
Post-Execution Reflection
After this skill completes, check before closing:
1. Did the command succeed? — If not, fix the instruction or error table that caused the failure. 2. Did parameters or output change? — If the underlying tool's interface drifted, update Usage examples and Parameters table to match. 3. Was a workaround needed? — If you had to improvise (different flags, extra steps), update this SKILL.md so the next invocation doesn't need the same workaround.
Only update if the issue is real and reproducible — not speculative.
Evolution Log
Convention: Reverse chronological order (newest on top, oldest at bottom). Prepend new entries.
---
2026-02-26: Initial Evolution Log
Status: Skill is in use and maintained. Track improvements here.
Purpose
This evolution log tracks updates to the skill. Each entry should note:
- What changed (content, structure, tooling)
- Why it changed (bug fix, feature request, best practice)
- Files affected
How to Use
1. When updating SKILL.md or references, add an entry here with the date 2. Keep entries reverse-chronological (newest first) 3. Link to ADRs or GitHub issues when relevant 4. Reference specific line changes when helpful
---