gitlab-managerManage GitLab repositories, merge requests, and issues via API. Use for tasks like creating repos, reviewing code in MRs, or tracking issues.
Install via ClawdBot CLI:
clawdbot install jorgermp/gitlab-managerThis skill allows interaction with GitLab.com via the API.
api scope must be set in the environment.Use the provided Node.js script to interact with GitLab.
scripts/gitlab_api.js
Create a new project in GitLab.
./scripts/gitlab_api.js create_repo "<name>" "<description>" "<visibility>"
# Visibility: private (default), public, internalList MRs for a specific project.
./scripts/gitlab_api.js list_mrs "<project_path>" "[state]"
# Project path: e.g., "jorgermp/my-repo" (will be URL encoded automatically)
# State: opened (default), closed, merged, allAdd a comment (note) to a specific MR. Useful for code review.
./scripts/gitlab_api.js comment_mr "<project_path>" <mr_iid> "<comment_body>"Open a new issue.
./scripts/gitlab_api.js create_issue "<project_path>" "<title>" "<description>"Create a private repo:
GITLAB_TOKEN=... ./scripts/gitlab_api.js create_repo "new-tool" "A cool new tool" "private"Review an MR:
# First list to find ID
GITLAB_TOKEN=... ./scripts/gitlab_api.js list_mrs "jorgermp/my-tool" "opened"
# Then comment
GITLAB_TOKEN=... ./scripts/gitlab_api.js comment_mr "jorgermp/my-tool" 1 "Great work, but check indentation."Generated Feb 24, 2026
A development team uses the skill to automate repository creation for new projects and manage merge requests during code reviews. It streamlines workflows by listing open MRs and adding review comments directly via API, reducing manual GitLab UI navigation.
In a CI/CD pipeline, this skill automates issue tracking and MR management post-deployment. It creates issues for bugs detected in production and comments on MRs with deployment status updates, enhancing operational efficiency.
Maintainers of open-source projects utilize the skill to handle incoming contributions by listing and commenting on merge requests. It helps manage community submissions efficiently, ensuring timely reviews and feedback.
Instructors in coding bootcamps use the skill to set up private repositories for students and track their progress through issues and MRs. It facilitates hands-on learning by automating project setup and feedback processes.
Large organizations employ the skill to oversee multiple GitLab projects, creating repositories for new initiatives and monitoring MRs across teams. It centralizes control and improves visibility into development activities.
Offer a managed service that integrates this skill into existing DevOps tools, providing automated GitLab management for clients. Revenue is generated through subscription fees based on usage tiers and support levels.
Provide consulting services to tailor the skill for specific enterprise needs, such as custom scripts or workflow optimizations. Revenue comes from project-based fees and ongoing maintenance contracts.
Develop training programs and certifications around using this skill for GitLab automation. Revenue is earned from course enrollments, workshops, and certification exams targeting IT professionals.
💬 Integration Tip
Ensure the GITLAB_TOKEN is securely stored in environment variables and test commands in a sandbox environment first to avoid accidental repository changes.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Query the DeepWiki MCP server for GitHub repository documentation, wiki structure, and AI-powered questions.
Automated GitHub PR code review with diff analysis, lint integration, and structured reports. Use when reviewing pull requests, checking for security issues,...
Essential Git commands and workflows for version control, branching, and collaboration.
Advanced git operations beyond add/commit/push. Use when rebasing, bisecting bugs, using worktrees for parallel development, recovering with reflog, managing subtrees/submodules, resolving merge conflicts, cherry-picking across branches, or working with monorepos.
Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.