monorepo-maintenance
Use when working in monorepos, workspaces, package boundaries, shared libraries, dependency graphs, Nx, Turborepo, pnpm/yarn/npm workspaces, Bazel, build caching, versioning, or cross-package refactors.
Works with
--- name: monorepo-maintenance description: Use when working in monorepos, workspaces, package boundaries, shared libraries, dependency graphs, Nx, Turborepo, pnpm/yarn/npm workspaces, Bazel, build caching, versioning, or cross-package refactors. license: MIT --- # Monorepo Maintenance ## Workflow 1. Identify workspace manager, package graph, build system, affected commands, and ownership boundaries. 2. Locate the smallest package set affected by the requested change. 3. Preserve public package contracts unless a coordinated breaking change is requested. 4. Update shared types, generated artifacts, and package exports together. 5. Avoid broad dependency bumps unless needed. ## Guidance - Use repo-native affected/test/build commands when available. - Keep shared libraries general and application-specific logic in applications. - Watch for duplicate dependencies, peer dependency drift, and circular imports. - Update docs or examples when package APIs change. ## Verification - Run affected lint, typecheck, test, and build commands. - Confirm package exports and imports still resolve. - Mention packages touched and any downstream risks.
More Git Workflows skills
git-commit
github/awesome-copilot
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
git-workflow-and-versioning
addyosmani/agent-skills
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump, tagging, or writing a changelog.
resolve-merge-conflicts
warpdotdev/common-skills
Resolve Git merge conflicts by extracting only unresolved paths, conflict hunks, and compact diffs instead of loading whole files into context. Use when a merge, rebase, cherry-pick, or stash pop stops on conflicts, when `git status` shows unmerged paths, or when files contain conflict markers.
