monorepo-cli
Manage the CLI tools monorepo using helper scripts. Use when checking CI status, release commits, or managing multiple CLI projects.
Works with
--- name: monorepo-cli description: Manage the CLI tools monorepo using helper scripts. Use when checking CI status, release commits, or managing multiple CLI projects. license: MIT --- # Monorepo CLI Cross-project management for the CLI tools monorepo. ## Overview This skill provides helper scripts for managing multiple CLI projects in the monorepo: - App-Store-Connect-CLI - Google-Drive-CLI - Google-Play-Developer-CLI - Grokipedia-CLI - App-StoreKit-CLI - App-Store-Server-CLI - Apple-Map-Server-CLI - MyMarketNews-CLI - cimis-cli ## Available Scripts ### check-ci-status.sh Check GitHub Actions CI status for all projects. ```bash # Human-readable output ./skills/monorepo-cli/scripts/check-ci-status.sh # JSON output for automation ./skills/monorepo-cli/scripts/check-ci-status.sh --json ``` **Output:** - Shows emoji indicators for each project - Success: ✅ - Failure: ❌ - No runs: ⚠️ - Unknown: ❓ ## Prerequisites - GitHub CLI (`gh`) installed and authenticated - Access to all monorepo repositories ## Agent Best Practices 1. **Check CI first** before releases 2. **Use JSON output** for automation 3. **Review all projects** - one failure can block releases
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.
