AI Plugin Indexplatform.gitlab.gitlab-cli-command-policy alternatives
The most used alternatives to platform.gitlab.gitlab-cli-command-policy are dagger-chores, prowler, sergo-examples. All are developer tools skills with an active GitHub repository, ranked below by GitHub stars and recent activity.
| # | Skill | What it does | Runs | Updated | Stars |
|---|---|---|---|---|---|
| ref | platform.gitlab.gitlab-cli-command-policy contrueCT | Use whenever GitLab CLI-backed capabilities are available so model behavior stays within wrapper tools, context budgets, and publishing permission boundaries. | Skill | 17 days ago | 7 |
| 1 | dagger-chores dagger | Handle quick, repeatable Dagger repository maintenance chores. Use when the user asks for small operational changes and wants the same established edits and commit style applied quickly. | Skill | today | 16k |
| 2 | prowler prowler-cloud | Main entry point for Prowler development - quick reference for all components. Trigger: General Prowler development questions, project overview, component navigation (NOT PR CI gates or GitHub Actions workflows). | Skill | today | 15k |
| 3 | sergo-examples github | Optional Sergo examples for cache formats and reporting templates. | Skill | today | 5.4k |
| 4 | code-review langchain-ai | Perform a structured code review of changes, checking for correctness, style, tests, and potential issues. | Skill | today | 30k |
| 5 | handle-pr-comments storybookjs | Triage and resolve GitHub PR review comments one by one, interactively. Use when the user asks to handle, address, respond to, or resolve PR review comments, or mentions reviewer feedback on a pull request. | Skill | today | 91k |
| 6 | unit-testing NativeScript | How to run and write unit tests in this workspace (Vitest, colocated .spec.ts files, mocked native globals). Use when writing, changing, or running tests. | Skill | yesterday | 26k |
| 7 | ov-ensure-coding-style openvinotoolkit | Detect and fix clang-format, clang-tidy, and copyright header violations in an OpenVINO C++ codebase. Use when the user complains about code style or formatting, asks to clean up changes, fix linting, add a copyright header, or when a style check or linting CI job is failing. Do not use for build errors, compilation failures, linker errors, test failures, runtime crashes, accuracy issues, or CMake config problems. | Skill | today | 11k |
| 8 | build-game-inventory MengTo | Build or repair game inventory, loot, equipment, tooltips, drag-and-drop, persistence, and progression systems. Use for item schemas, pickup flows, stack rules, equipment slots, atomic swaps, save migration, and no-loss regression testing. | Skill | 2 days ago | 6.9k |
| 9 | tidb-bazel-prepare-gate pingcap | Use when deciding whether make bazel_prepare is required before build or test commands based on local file changes in TiDB. | Skill | today | 41k |
| 10 | frb-debugging fzyzcjy | Use when generated code looks wrong, code generation fails, or you need to understand FRB internals | Skill | yesterday | 5.5k |
| 11 | fix-members-short-description flet-dev | Use when asked to fix short descriptions of Python type members. | Skill | yesterday | 17k |
| 12 | conversion-issues openvinotoolkit | Investigate and fix model conversion issues in OpenVINO Frontends (ONNX, PyTorch) — triage, debugging, accuracy comparison, and pre-submission verification. | Skill | today | 11k |
Questions
What is the best alternative to platform.gitlab.gitlab-cli-command-policy?
By usage, dagger-chores is the most popular alternative, with 16k GitHub stars. The right choice depends on which features and hosting you need.
Is platform.gitlab.gitlab-cli-command-policy still maintained?
Its last commit was 17 days ago. You can see current activity on its listing page.