Mermaid gitlab mr size rules
Skill kjuhwa/skills-hub/skills/workflow/mermaid-gitlab-mr-size-rules
Self-correcting knowledge corpus for Claude Code — 9 stable shape clusters, bias-correction pipeline baked into contribution flow. 47 papers, 45 techniques, 1.1k skills.
npx -y skills add kjuhwa/skills-hub --skill mermaid-gitlab-mr-size-rulesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Keep Mermaid diagrams in GitLab MRs readable — cap nodes, avoid nested subgraphs, quote IDs with special chars, connect all subgraphs
SKILL.md
1.4 KB, as published. Nobody here has run it
Mermaid for GitLab MRs
Trigger
- Authoring a merge-request description with embedded Mermaid.
- Reviewing an MR where the diagram renders tiny or unreadable.
Steps
- Cap at 10 nodes / 2 subgraphs / 6-step chains / 5–6 sequence participants per diagram. If you exceed, split into multiple diagrams by concept.
- No nested subgraphs. GitLab shrinks them aggressively.
- All subgraphs must be connected by at least one edge — isolated subgraphs render tiny.
- Subgraph IDs: alphanumeric only. Put human labels in brackets:
subgraph AuthModule[auth-module]. Never put-,/, or spaces in the ID. - Node text: avoid
/, unescaped quotes. Wrap in"..."if the label needs punctuation. - Layout choice:
- Sequential steps (4+):
LR - Branching / parallel / ER:
TB - Before/After compare, state:
LR
- Sequential steps (4+):
- Place the diagram inside the "리뷰어를 위한 설명" section of the MR template.
Pre-merge check
- Preview the rendered MR in GitLab, not just the IDE.
- If any subgraph is unreadable at GitLab's default width, split the diagram.