gitlab-issue-tracker
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Use whenever the user references a GitLab issue by its short ID (e.g. "#5", "#12", "issue 7", "task #3") and wants work done against it — phrases like "work on #5", "start #12", "execute issue 7", "implement #3 and #4", "pick up #9", "let's tackle the next issue", or any agent/subagent dispatch that should be tied to a GitLab issue's lifecycle. The skill takes ownership of the issue's state: it parses the ID, fetches the issue via `glab` CLI or the GitLab REST API (using the project's `.gitlab-taskboard.json` config), moves it to "In Progress", auto-ticks acceptance-criteria checkboxes as the work that satisfies each one is completed (announcing each tick), and after all AC are met asks the user to confirm closing — then closes the issue and posts a short summary comment. Use it as a wrapper around any execution flow so the GitLab board stays a faithful mirror of what the agent actually did.
In this repository5 other files it gives its agents.
- askSkill
- files-to-deploySkill
- gitlab-issue-creatorSkill
- req-to-mdSkill
- research-webSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
21 rules. About 0 are common, 17 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈17
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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
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.