Cursor rule Cursor
Read a GitLab issue, identify the root cause (not just symptoms), surface real risks, and produce an implementation approach before writing any code.
A portable workflow skills library for GitLab teams. Works across Claude Code, Cursor, and Codex. Covers two full loops: one for PMs and designers, one for engineers — from rough idea to confirmed-resolved issue.
Cursor rule Cursor
Read a GitLab issue, identify the root cause (not just symptoms), surface real risks, and produce an implementation approach before writing any code.
Cursor rule Cursor
Create a GitLab Merge Request — clear title, high-level summary of what was changed and why, explicit confirmation the issue is resolved.
Cursor rule Cursor
Full GitLab development loop — from issue to confirmed-resolved. Covers write-issue, analyze-issue, fix-issue, review-code, create-mr, summarize-issue, triage-issue, and post-merge verification.
Cursor rule Cursor
Implement a fix following the human-thinking loop — understand the root cause, plan the minimal change, implement, verify the problem is actually gone.
Cursor rule Cursor
Wire up GitLab API access — multiple instances, project aliases, tokens. Run this once before any other GitLab skill.
Cursor rule Cursor
Full PM/designer loop — draft an issue, interact with users and stakeholders to validate it, refine until dev-ready, then finalize.
Cursor rule Cursor
Pre-MR self-review — first confirm the problem is actually solved, then check for security, correctness, and simplicity.
Cursor rule Cursor
After an issue is fixed and its MR is created, summarize the work in high-level markdown and post it as a comment on the GitLab issue.
Cursor rule Cursor
Use when replying to comments on a GitLab issue, or when an issue has comments that might tag you or be waiting on your reply as assignee — figures out which comments genuinely need a response, drafts each reply grounded in the codebase, and posts after you confirm.
Cursor rule Cursor
Turn a rough idea into a well-structured GitLab issue with clear problem statement, root cause, and testable acceptance criteria.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: