Skill Claude CodeCodex
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.
This repository also configures its own agents. See what encore-skills tells them →
Skill Claude CodeCodex
Read a GitLab issue, identify the root cause (not just symptoms), surface real risks, and produce an implementation approach before writing any code.
Skill Claude CodeCodex
Create a GitLab Merge Request — clear title, high-level summary of what was changed and why, explicit confirmation the issue is resolved.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
Implement a fix following the human-thinking loop — understand the root cause, plan the minimal change, implement, verify the problem is actually gone.
Skill Claude CodeCodex
Wire up GitLab API access — multiple instances, project aliases, tokens. Run this once before any other GitLab skill.
Skill Claude CodeCodex
Full PM/designer loop — draft an issue, interact with users and stakeholders to validate it, refine until dev-ready, then finalize.
Skill Claude CodeCodex
Pre-MR self-review — first confirm the problem is actually solved, then check for security, correctness, and simplicity.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
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: