zereight/gitlab-skill

Dernière activité source enregistrée: 3 mai 2026 à 15:48

Catalogue SkillsMP mis à jour: 5 novembre 2026 à 19:57

skills collectés: 1

Étoiles GitHub: 0
Forks GitHub: 0

Installer avec un assistant IA

Copiez ce prompt dans l’assistant IA que vous utilisez.

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/zereight/gitlab-skill.

README du dépôt

Fichier source du README : README.md

Lire le README source

Afficher le README complet

# GitLab Skill User Guide Translations: [한국어](README.ko.md) | [中文](README.zh.md) This folder contains an agent skill that lets you read GitLab information and post comments without running a GitLab MCP server. Non-developers can use it by copying and running the commands below in Terminal. ## Install with skills Install this skill globally for all supported agents: ```shell npx -y skills add <repository-url> -s gitlab-skill --all -g ``` For a local checkout: ```shell cd /Users/tao.exe/Documents/gitlab-skill npx -y skills add . -s gitlab-skill --all -g ``` If npm cache permission errors appear, use a temporary cache: ```shell NPM_CONFIG_CACHE=/private/tmp/skills-cache npx -y skills add . -s gitlab-skill --all -g ``` To install only for one agent, replace `--all` with `-a <agent-name>`. ## 1. What You Need You need 3 things. 1. A GitLab account 2. A GitLab Personal Access Token 3. Node.js 18 or later Check whether Node.js is installed: ```shell node --version ``` `v18` or later is OK. ## 2. Create a GitLab Token Create a Personal Access Token in GitLab. 1. Open GitLab 2. Click your profile in the top-right corner 3. Go to Preferences or Edit profile 4. Open Access Tokens 5. Create a new token 6. Select the `api` scope in most cases 7. Copy the generated token Treat the token like a password. Do not share it in chat, documents, or screen recordings. ## 3. Set the Token Run this in Terminal: ```shell export GITLAB_PERSONAL_ACCESS_TOKEN="paste_your_token_here" ``` If you use a company GitLab instead of GitLab.com, also set the API URL: ```shell export GITLAB_API_URL="https://gitlab.example.com/api/v4" ``` Replace `gitlab.example.com` with your company's GitLab host. ## 4. Open This Folder Run: ```shell cd /Users/tao.exe/Documents/gitlab-skill ``` ## 5. Check the Connection Check that your GitLab account can be read: ```shell node scripts/gitlab_api.mjs me ``` If it works, your account information will be printed as JSON. If token errors appear, check: - You ran `export GITLAB_PERSONAL_ACCESS_TOKEN="..."` in the current Terminal window - The token has the `api` scope ## 6. Project Name Format You can use either a numeric project ID or a project path. Examples: ```text 123456 group/project group/subgroup/project ``` If the GitLab URL is: ```text https://gitlab.example.com/bank/mobile-app ``` Use this project value: ```text bank/mobile-app ``` ## 7. Common Commands List open merge requests: ```shell node scripts/gitlab_api.mjs list-mrs "group/project" --state opened --per-page 30 ``` Get one merge request: ```shell node scripts/gitlab_api.mjs get-mr "group/project" 12 ``` List changed files in a merge request: ```shell node scripts/gitlab_api.mjs mr-files "group/project" 12 ``` View merge request diff: ```shell node scripts/gitlab_api.mjs mr-diffs "group/project" 12 --unidiff true ``` List merge request comments: ```shell node scripts/gitlab_api.mjs mr-notes "group/project" 12 ``` Post a general merge request comment: ```shell node scripts/gitlab_api.mjs create-mr-note "group/project" 12 --body "Checked." ``` List open issues: ```shell node scripts/gitlab_api.mjs list-issues "group/project" --state opened --per-page 30 ``` Get one issue: ```shell node scripts/gitlab_api.mjs get-issue "group/project" 34 ``` List issue comments: ```shell node scripts/gitlab_api.mjs issue-notes "group/project" 34 ``` Post an issue comment: ```shell node scripts/gitlab_api.mjs create-issue-note "group/project" 34 --body "Checked." ``` Read a file: ```shell node scripts/gitlab_api.mjs file "group/project" "README.md" --ref main ``` Search code: ```shell node scripts/gitlab_api.mjs search-code "group/project" --search "search term" --ref main ``` List pipelines: ```shell node scripts/gitlab_api.mjs pipelines "group/project" --ref main --per-page 10 ``` List jobs in a pipeline: ```shell node scripts/gitlab_api.mjs jobs "group/project" 123456 ``` View a job log: ```shell node scripts/gitlab_api.mjs job-log "group/project" 987654 ``` ## 8. Ask an AI Agent to Use It You can ask your AI agent like this: ```text Use $gitlab-skill to review MR 12 in group/project. Do not use MCP. ``` Or: ```text Use $gitlab-skill to list open MRs in group/project. ``` ## 9. Important Notes - Comment commands write real comments to GitLab. - Do not save your token in documents. - If the output is too long, reduce the result count with `--per-page 10`. - For company GitLab instances, you may need to set `GITLAB_API_URL`. ## 10. Troubleshooting `Missing GitLab token`: ```shell export GITLAB_PERSONAL_ACCESS_TOKEN="paste_your_token_here" ``` `401 Unauthorized`: - The token is wrong or expired. - Check that the token has the `api` scope. `404 Not Found`: - The project path may be wrong. - Your account may not have access to the project. If you use company GitLab but requests go to GitLab.com: ```shell export GITLAB_API_URL="https://your_company_gitlab_host/api/v4" ```

Chargement du README du dépôt…

Skills dans ce dépôt

Développeurs de logiciels

1 catégories métier · 100% classifié

skill

métier

description

mis à jour

gitlab-skill

Développeurs de logiciels

Use this skill to inspect and operate GitLab projects without MCP by calling the GitLab REST API directly. Use it for GitLab merge requests, issues, repository files, code search, pipelines, jobs, and review comments when a GitLab token is available.

Langue du texte source : anglais

2026-05-03

Affichage de 1 skills collectés sur 1.