Maarten Kuiper

You can enforce Git branch naming rules when branching or committing, write GitHub pull requests with English changelog-ready titles and Dutch template-based bodies, produce design documents for non-trivial code changes before implementation, and conduct structured PR reviews validated against Notion tickets.

Software developers and engineers working in Git and GitHub repositories who need consistent branch naming, standardized bilingual PR descriptions, architecture planning before non-trivial builds or refactors, and disciplined code review practices with severity and confidence labels.

Use design-first for non-trivial builds or refactors whose shape is not obvious: it investigates context, compares architecture alternatives, writes a design document, and iterates until user approval. Skip it for trivial changes, pure debugging, or already-approved approaches.

It checks the PR against its Notion ticket, relies on CI instead of re-running tests, and posts every finding as one grouped GitHub review. Each comment follows required language, style, severity and confidence labels, plus a mandated footnote.

You need a Git repository hosted on GitHub, since the skills govern branch creation, gh pr create and gh pr review operations. The pr-review skill additionally expects a linked Notion ticket and an existing CI pipeline to validate changes.