Skip to content
Skills Library
Programming · Research

gitlab-explorer

/gitlab-explorer

Explore GitLab repositories using glab CLI and git commands. Use when user asks to: clone repositories, search projects or code in GitLab, view merge requests, explore project structure, check CI/CD pipelines, work with issues, or analyze git history. IMPORTANT: Always run authentication check script first before any GitLab operation.

Licence
Apache-2.0
Last repository change
06.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
1
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 06.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/check_gitlab_auth.sh

What it does and when to use it

Explore GitLab repositories using glab CLI and git commands. Use when user asks to: clone repositories, search projects or code in GitLab, view merge requests, explore project structure, check CI/CD pipelines, work with issues, or analyze git history. IMPORTANT: Always run authentication check script first before any GitLab operation.

Original author description

Explore GitLab repositories using glab CLI and git commands. Use when user asks to: clone repositories, search projects or code in GitLab, view merge requests, explore project structure, check CI/CD pipelines, work with issues, or analyze git history. IMPORTANT: Always run authentication check script first before any GitLab operation.

How it works

  1. Before Any GitLab Operation
  2. Quick Start
  3. Exploring Code
  4. Working with Merge Requests
  5. CI/CD Pipelines
  6. Issues
  7. Reference Materials
  8. Common Workflows
Original SKILL.md headings · 171 lines, 513 words
SKILL.md preview
---
name: gitlab-explorer
description: "Explore GitLab repositories using glab CLI and git commands. Use when user asks to: clone repositories, search projects or code in GitLab, view merge requests, explore project structure, check CI/CD pipelines, work with issues, or analyze git history. IMPORTANT: Always run authentication check script first before any GitLab operation."
---

# GitLab Explorer

This skill enables exploring GitLab repositories, searching code, viewing merge requests, and working with git history.

## Before Any GitLab Operation

**ALWAYS run the authentication check first:**

```bash
bash /mnt/skills/public/gitlab-explorer/scripts/check_gitlab_auth.sh
```

This script will:
- Verify if GitLab token is configured
- Validate the token by calling GitLab API
- Show logged-in user info if valid
- Provide setup instructions if not configured

**DO NOT** try to read or echo `$GITLAB_TOKEN` directly - the script handles validation securely without exposing the token.

If authentication is not configured, inform the user:
> To use GitLab features, please go to  and add your GitLab Personal Access Token. Then start a NEW chat to apply the token.

## Quick Start

### Clone a Repository

```bash
git clone https://gitlab.com/group/project.git
cd project
```

### Search for Projects

```bash
# Search projects by name
glab api "projects?search=keyword" | jq '.[].path_with_namespace'

# List projects in a group
glab api "groups/GROUP_NAME/projects" | jq '.[].name'
```

### Check Current User

```bash
glab api user | jq '{username, email, name}'
```

## Exploring Code

### Repository Structure

```bash
# Show directory tree
tree -L 2

# Find files by pattern
find . -name "*.py" -type f

# Search for text in files
git grep "pattern"
```

### Git History

```bash
# View commit history
git log --oneline -20

# Visual branch history
git log --oneline --graph --all -20

# Who changed what
git blame filename

# Show specific commit
git show COMMIT_HASH

# Changes between branches
git diff main..feature-branch
```

### Top Contributors

```bash
git shortlog -sn --all | head -10
```

## Working with Merge Requests

```bash
# List open MRs
glab mr list

# View specific MR
glab mr view 123

# Show MR diff
glab mr diff 123

# Checkout MR branch locally
glab mr checkout 123
```

## CI/CD Pipelines

```bash
# Current pipeline status
glab ci status

# List recent pipelines
glab ci list

# View pipeline details
glab ci view PIPELINE_ID

# Watch job logs in real-time
glab ci trace
```

## Issues

```bash
# List issues
glab issue list

# View issue details
glab issue view 123

# Create new issue
glab issue create --title "Bug report" --description "Description here"
```

## Reference Materials

For detailed command reference, see:
- `references/glab-commands.md` - Complete glab CLI reference
- `references/git-commands.md` - Git commands for code exploration

## Common Workflows

### Explore Unknown Repository

1. Clone the repo
2. Check README and documentation
3. Explore directory structure with `tree`
4. Find main entry points
5. Use `git log` to understand recent changes
6. Use `git blame` to find who wrote specific code

### Review Merge Request

1. `glab mr view ID` - read description
2. `glab mr diff ID` - review changes
3. `glab mr checkout ID` - test locally if needed
4. Check CI status with `glab ci status`

### Find Code by Pattern

```bash
# Search in all files
git grep "function_name"

# Search with context
git grep -n -C 3 "pattern"

# Search in specific file types
git grep "pattern" -- "*.py"
```
Files in this package (4)
  • SKILL.md 3 KB
  • references/git-commands.md 5 KB
  • references/glab-commands.md 4 KB
  • scripts/check_gitlab_auth.sh 4 KB

Versions

The database has no other skills named gitlab-explorer.

Database snapshot: 13.11.2026 · package version c6cf5fb891d5 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100gitlab
    GitLab issues, merge requests, repositories, CI pipelines, and code search via the glab CLI. Use when the user mentions GitLab, an MR/issue number, a project on gitlab.com, or a self-hosted GitLab instance.
  • 100glab
    Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
  • 100glab
    Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
  • 100gitlab
    Create and manage GitLab issues, merge requests, pipelines, and repositories using the glab CLI. Use when asked to open an MR, review a merge request, check CI/CD pipelines, list issues, or manage code review on GitLab.
  • 90gitlab-cli
    Reference guide for GitLab CLI (glab) commands. Use when running glab commands for issues, merge requests, pipelines, releases, or CI/CD operations, or when the user asks about GitLab CLI syntax.
  • 100glab
    Use when creating, reading, updating, or closing GitLab issues and merge requests with the glab CLI.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.