microsoft rushstack
OFFICIALLABSCO SUMMARY
The skill, rushstack-best-practices, is scoped to one job: helping with a Rush-based monorepo — installing, updating, building, and rebuilding, choosing which projects to touch, managing dependencies, tuning build caching, configuring subspaces, and troubleshooting Rush-specific failures, per its own description. microsoft/rushstack is the home for several published tools, and its own documentation links list Rush, Heft, API Extractor, API Documenter, Lockfile Explorer, and TSDoc as separate projects under the same roof — but only the Rush tool gets a skill here.
This is for teams already running Rush to manage a large TypeScript monorepo, and it has essentially nothing for anyone else. If you don't use Rush, the commands, subspace configuration, and dependency conventions this skill teaches don't apply to your build.
READ THE FULL ANALYSIS
One skill covering one tool in a much larger monorepo. Heft, API Extractor, API Documenter, and Lockfile Explorer each have their own published documentation per the repository's doc-links list, but none of them has a skill of its own here — only Rush does.
ALSO IN THIS PACKAGE
playwright
stdio · node ${workspaceFolder}/apps/playwright-browser-tunnel/lib/PlaywrightMcpBrowserTunnelClientCommandLine.jsWHAT'S INSIDE
1 showing · 1 totalrushstack-best-practices
In a codebase where Rush manages many projects at once, the familiar npm or yarn commands cause trouble — this says which Rush command to reach for instead, and how to rebuild only the part you touched.
HOW TO GET IT
npx skills add microsoft/rushstacknpx skills add microsoft/rushstack --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.