mikeparcewski/wicked-garden-platform-glab-cli
skills/platform/glab-cli/SKILL.md
Use when you need glab CLI patterns for GitLab — pipeline debugging, MR management, or release automation. Provides composable glab invocations for power users. NOT for GitHub (use the gh-cli skill) or simple git commands (use Bash).
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden wicked-garden-platform-glab-cliInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 13, 2026, 7:57 AM117.9s5 files scanned
SKILL.md
- name:
- wicked-garden-platform-glab-cli
- description:
- |
- phase_relevance:
- ["build", "review", "operate"]
- archetype_relevance:
- ["*"]
GitLab CLI Power Utilities
Intelligent wrappers and patterns for GitLab CLI operations.
When to Use
- Debugging failed GitLab CI/CD pipelines
- Managing merge requests across projects
- Automating releases
- Bulk operations on issues/MRs
- Project health checks
Prerequisites
# macOS
brew install glab
# Or download from https://gitlab.com/gitlab-org/cli
# Authenticate
glab auth login
Core Capabilities
1. Pipeline Debugging
Get actionable errors from failed pipelines.
# Diagnose most recent failure
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/skills/platform/glab-cli/scripts/glab_ops.py" diagnose
# Specific project
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/skills/platform/glab-cli/scripts/glab_ops.py" diagnose --project group/project
# With suggested fixes
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/skills/platform/glab-cli/scripts/glab_ops.py" diagnose --suggest-fixes
Output: Job failures, error excerpts, timing info.
2. MR Operations
Merge request management at scale.
# List MRs needing review
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/skills/platform/glab-cli/scripts/glab_ops.py" mr-review-queue
# MRs ready to merge (approved + passing)
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/skills/platform/glab-cli/scripts/glab_ops.py" mr-merge-ready --dry-run
# MR health check
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/skills/platform/glab-cli/scripts/glab_ops.py" mr-status 123
3. Release Automation
Create releases with changelogs.
# Preview release
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/skills/platform/glab-cli/scripts/glab_ops.py" release --dry-run
# Create minor release
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/skills/platform/glab-cli/scripts/glab_ops.py" release --bump minor
# With custom notes
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/skills/platform/glab-cli/scripts/glab_ops.py" release --notes "Breaking: API v2"
Quick Patterns
# Watch pipeline
glab ci view --live
# Retry failed jobs
glab ci retry
# View job logs
glab ci trace <job-id>
# Create MR from current branch
glab mr create --fill
# Checkout MR locally
glab mr checkout 123
# View MR changes
glab mr diff 123
# Approve MR
glab mr approve 123
# Merge MR
glab mr merge 123 --squash --remove-source-branch
glab vs gh Quick Reference
| Task | GitHub (gh) | GitLab (glab) |
|------|-------------|---------------|
| Create PR/MR | gh pr create | glab mr create |
| List CI runs | gh run list | glab ci list |
| View CI logs | gh run view --log | glab ci trace |
| Watch CI | gh run watch | glab ci view --live |
| Retry CI | gh run rerun --failed | glab ci retry |
| Checkout PR/MR | gh pr checkout 123 | glab mr checkout 123 |
Integration
Works with:
- wicked-garden:search: Find code, create issues via glab
- Native tasks: Track MR status alongside tasks via TaskUpdate description appends
References
refs/glab-ops.md- Full script documentationrefs/patterns.md- Common workflow patternsrefs/ci-debugging.md- Pipeline troubleshooting
Related Skills
mikeparcewski/wicked-garden-engineering-conformance-reviewer
development
VerifiedTrustedCommunity
Pattern-conformance agent-half: evaluates a produced artifact or diff against a set of architectural/design pattern rules from the conformance-rule store (wicked_governance schema). Returns structured findings with rule ID, severity, and rationale — the deterministic half (mechanical rule recall) is done by the guard pipeline; this is the semantic evaluation step. Triggered by: the guard_pipeline `outgov_pattern` check (session-close), or explicitly by an engineering review when WICKED_OUTGOV_RULES_DIR is populated. NOT a replacement for the full `engineering` review skill — focuses only on conformance to stored Pattern rules; architecture and code-quality checks live in the `engineering` skill. Semantic evaluation reuses `wicked-garden-qe-semantic-reviewer` as the designated agent-half evaluator (per garden#983 spec). This skill is the orchestrating wrapper that loads applicable Pattern rules and delegates the per-rule semantic judgment to qe-semantic-reviewer.
8SKILL.mdUpdated Jul 22, 2026
mikeparcewski/wicked-garden-domain
tools
VerifiedTrustedCommunity
The FOUNDATIONAL domain-model capability: extract a codebase's domain — testable business rules (with confidence + provenance), entities, requirements — as a schema-conformant model on the estate graph. The workers annotate the store; wicked-core reads it and builds the requirements graph, coverage-gating fail-closed. Steers three fork workers. A shared substrate, not a modernization tool. The `modernize` archetype DERIVES from it; build / migrate / review / specify / explore consume the SAME domain model — none OWN it. Understanding a codebase's domain is upstream of almost everything else garden does. Use when: "extract the business rules / domain model from this codebase", "build a requirements graph from the code", "what does this system actually require", "reverse-engineer the domain before we build/port/migrate". Works on ANY codebase (modern or legacy) — the value is the domain model, not the porting. NOT the code transform itself (that is the archetype consuming this model). This skill produces the DOMAIN MODEL, not new code.
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-modeler
development
VerifiedTrustedCommunity
Domain-graph fork worker for the modernize archetype. Groups the estate's Louvain communities into business domains, attaches each requirement to its cluster (advisory cluster_id provenance), and invokes wicked-core's domain-graph build (which reads the annotated estate store, recomputes coverage fail-closed, and builds the requirements graph) — then validates core's output against the vendored schema. Use when: dispatched by wicked-garden-domain after rule extraction to turn a flat rule set into cluster-keyed domains; "group these into domains", "build the requirements graph", "translate clusters into a domain model". NOT for mining the rules themselves (that is domain-extractor) or threat-modeling (that is domain-coverage).
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-extractor
tools
VerifiedTrustedCommunity
Rule-extraction fork worker for the FOUNDATIONAL domain-model capability. Mines testable business rules from a codebase — each with a numeric confidence and a provenance{source, ref, source_kinds} — and annotates them into the estate store so wicked-core can build the domain-model requirements graph (coverage-gated). This is a substrate, not a modernization tool: the `modernize` archetype DERIVES from it, and build / migrate / review / specify / explore can consume the same domain model — none OWN it. Use when: dispatched by wicked-garden-domain to mine the business_rules of a codebase (or a module); "extract the domain rules", "what does this system require", building the requirements half of a domain model. NOT for grouping into domains (that is domain-modeler) or judging coverage (that is domain-coverage — a seat-distinct evaluator).
8SKILL.mdUpdated Jul 15, 2026