gitlab
GitLab operations via glab CLI. Use when user mentions: MR, merge request, gitlab issue, pipeline, CI status, glab, or when git remote shows gitlab.com or self-hosted GitLab.
What this skill does
# GitLab CLI (glab) ## When to Use This Skill Use `glab` for GitLab repositories. To detect GitLab: ```bash git remote -v | grep -i gitlab ``` If the remote contains `gitlab.com` or a known GitLab instance, use this skill. ## Before Any Operation Always verify authentication first: ```bash glab auth status ``` If not authenticated, guide the user to run `glab auth login`. ## Behavioral Guidelines 1. **Creating MRs**: Always check for uncommitted changes first with `git status` 2. **Viewing MRs/Issues**: Prefer `--comments` flag when user wants full context 3. **CI Operations**: Check `glab ci status` before suggesting `glab ci run` 4. **Use `--web`**: When the user might benefit from the browser UI ## Command Reference ### Merge Requests | Action | Command | |--------|---------| | Create | `glab mr create --title "Title" --description "Desc"` | | Create draft | `glab mr create --draft --title "Title"` | | List | `glab mr list` | | View | `glab mr view <id>` | | View with comments | `glab mr view <id> --comments` | | Checkout | `glab mr checkout <id>` | | Merge | `glab mr merge <id>` | | Approve | `glab mr approve <id>` | ### Issues | Action | Command | |--------|---------| | Create | `glab issue create --title "Title" --description "Desc"` | | List | `glab issue list` | | List mine | `glab issue list --assignee=@me` | | View | `glab issue view <id>` | | Close | `glab issue close <id>` | | Comment | `glab issue note <id> --message "Comment"` | ### CI/CD Pipelines | Action | Command | |--------|---------| | Status | `glab ci status` | | List | `glab ci list` | | View logs | `glab ci trace` | | Run new | `glab ci run` | | Retry failed | `glab ci retry` | ### Repository | Action | Command | |--------|---------| | View info | `glab repo view` | | Clone | `glab repo clone <repo>` | | Open in browser | `glab repo view --web`|
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.