agentleFS
Sign inStart free
akunzaiakunzai/agent-skills/skills/gitlab-epic/SKILL.md

gitlab-epic

Skill5 starsChanged 54 days agoMITView on GitHub

Use ONLY when a git repository is hosted on GitLab to create, structure, or link GitLab epics, sub-issues, and issue relations.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify GitLab hosting (git remote get-url origin.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

GitLab Epic & Issue Relations

For general glab syntax and gotchas, consult the official skill (glab skills install --global).

Preflight & Tier Check

Verify GitLab hosting (git remote get-url origin; custom domains: hosting-detection.md). Epics are Premium/Ultimate and live on the group, not the project. Probe before emitting any epic command:

glab api version                             # "enterprise": false => CE / Free
glab api "groups/<group>"                    # 200 => the group path is right
glab api "groups/<group>/epics?per_page=1"   # 403 or 404 => no native epics

Probe the group first — a 404 from the epics endpoint is otherwise indistinguishable from a mistyped path. Either code means no native epics: CE 19.3.2 answers 404, 403 is a paid tier answering a token with project but no group access. Both take Strategy B.

Epics API: deprecated since 17.0, removed in API v5. On 18.1+ use the Work Items API (work-items.md).

Tier Strategies

Strategy A: Premium / Ultimate (Native Wiring)

# Group epics & child issue links
glab api groups/:group_id/epics
glab api --method POST groups/:group_id/epics/:epic_iid/issues/:issue_id

# Issue links. relates_to is Free-tier; blocks / is_blocked_by need Premium.
glab api --method POST projects/:id/issues/:issue_iid/links \
  -f target_project_id=<target_project> -f target_issue_iid=<target_iid> -f link_type=blocks

An epic or group work item has no project context: #123 and !456 render as literal text there. Write group/project#123 or the full URL.

Strategy B: Free / CE Tier

Choose:

  • Native Work Items (GraphQL): real parent-child wiring on CE (Issue -> Task conversion, mutations, link constraints) — work-items.md.
  • Emulation: an ordinary issue plays the epic, wired up with relates_to links, markdown checklists (Part of #100), and the scoped labels type::epic, epic::<epic-name>, parent::<issue_id> — ce-emulation.md carries the commands and the taxonomy audit.

Measurements

An epic that records numbers states in its own body where each came from and when a row may be added; otherwise the next agent fills the table from whatever is at hand and the rows stop being comparable.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free