# Fetch Gitlab Issue Details

> Use when technical-support weekly-report data contains GitLab Issue URLs and the corresponding comments must be fetched through the GitLab GraphQL API.

- Skill: `huruizhi/fetch-gitlab-issue-details` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add huruizhi/fetch-gitlab-issue-details`
- Raw SKILL.md: https://api.skillmd.com/api/skills/huruizhi/fetch-gitlab-issue-details/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: huruizhi (https://skillmd.com/u/huruizhi)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/huruizhi/fetch-gitlab-issue-details

---


# Fetch GitLab Issue Details

Read either an Issue array or the `items` object produced by `query-tech-support-issues`. Deduplicate the Issue/engineer rows before calling GitLab.

Set `GITLAB_TOKEN` or pass `--token`. Optionally set `GITLAB_GRAPHQL_ENDPOINT` and `GITLAB_PROJECT_PATH`. Never store access tokens in this Skill.

```bash
python3 implementation.py \
  --input /tmp/weekly-report/01-issues.json \
  --output /tmp/weekly-report/02-issue-details.json
```

Derive the project path from each Issue URL when possible. Use the configured project path only as a fallback.