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.
2 12d ago A 28 tokens
original MIT
create-mr
02Cursor rule Cursor
Create a GitLab Merge Request — clear title, high-level summary of what was changed and why, explicit confirmation the issue is resolved.
2 12d ago A 26 tokens
original MIT
eng-workflow
03Cursor 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.
2 12d ago A 48 tokens
original MIT
fix-issue
04Cursor 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.
2 12d ago A 27 tokens
original MIT
Cursor rule Cursor
Wire up GitLab API access — multiple instances, project aliases, tokens. Run this once before any other GitLab skill.
2 12d ago A 25 tokens
original MIT
pm-workflow
06Cursor rule Cursor
Full PM/designer loop — draft an issue, interact with users and stakeholders to validate it, refine until dev-ready, then finalize.
2 12d ago A 26 tokens
original MIT
review-code
07Cursor rule Cursor
Pre-MR self-review — first confirm the problem is actually solved, then check for security, correctness, and simplicity.
2 12d ago A 23 tokens
original MIT
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.
2 12d ago A 29 tokens
original MIT
triage-issue
09Cursor 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.
2 12d ago A 54 tokens
original MIT
write-issue
10Cursor rule Cursor
Turn a rough idea into a well-structured GitLab issue with clear problem statement, root cause, and testable acceptance criteria.
2 12d ago A 25 tokens
original MIT
Instructions file CodexOpenCode
Instructions for encoreshao/encore-skills, covering available skills and skills.
2 12d ago A 618 tokens
original MIT
Instructions file
Instructions for encoreshao/encore-skills, covering encore-skills, structure, adding a skill and skills follow the human-thinking workflow.
2 12d ago A 332 tokens
original MIT
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.
2 12d ago A 33 tokens
original MIT
create-mr
14Skill Claude CodeCodex
Create a GitLab Merge Request — clear title, high-level summary of what was changed and why, explicit confirmation the issue is resolved.
2 12d ago A 30 tokens
original MIT
eng-workflow
15Skill 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.
2 12d ago A 52 tokens
original MIT
fix-issue
16Skill 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.
2 12d ago A 31 tokens
original MIT
Skill Claude CodeCodex
Wire up GitLab API access — multiple instances, project aliases, tokens. Run this once before any other GitLab skill.
2 12d ago B 29 tokens
original MIT
pm-workflow
18Skill Claude CodeCodex
Full PM/designer loop — draft an issue, interact with users and stakeholders to validate it, refine until dev-ready, then finalize.
2 12d ago A 30 tokens
original MIT
review-code
19Skill Claude CodeCodex
Pre-MR self-review — first confirm the problem is actually solved, then check for security, correctness, and simplicity.
2 12d ago A 26 tokens
original MIT
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.
2 12d ago A 35 tokens
original MIT
triage-issue
21Skill 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.
2 12d ago A 59 tokens
original MIT
write-issue
22Skill Claude CodeCodex
Turn a rough idea into a well-structured GitLab issue with clear problem statement, root cause, and testable acceptance criteria.
2 12d ago A 29 tokens
original MIT