Code pull request
Manage GitHub pull requests or GitLab merge requests: create, read/leave/respond to comments, and merge. Triggers on "open a PR", "make a PR", "merge this PR", "merge the MR", "read PR comments", "leave a comment on the PR", "respond to a comment", "ship this", or when a feature branch is ready for review.From its SKILL.md
npx -y skills add martinffx/atelier --skill code-pull-requestAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.7 KB, 321 tokens by cl100k_base, as published. Nobody here has run it
Pull Request / Merge Request Skill
Create, comment on, and merge GitHub pull requests or GitLab merge requests for the
current branch. Assumes the relevant CLI (gh or glab) is installed and authenticated.
This skill is create/read + write-gated. Every write action (create PR, leave comment, respond to comment, merge) requires explicit human confirmation before running.
Start Here
- Detect the platform and find the current branch's open PR/MR — see references/common.md.
- Pick a workflow:
| Workflow | Reference | Trigger phrases |
|---|---|---|
| Create PR/MR | create-pr.md | "open a PR", "make a PR", "submit for review" |
| Read comments | read-comments.md | "read PR comments", "show MR comments" |
| Leave a comment | leave-comment.md | "leave a comment", "comment on the PR" |
| Respond to a comment | respond-to-comment.md | "respond to a comment", "reply on the PR" |
| Merge PR/MR | merge-pr.md | "merge this PR", "ship it", "merge the MR" |
Both GitHub (gh) and GitLab (glab) are first-class. Every write step pauses for
human approval before running the CLI command.
What ships with it: 7 files
13.4 KB alongside SKILL.md
references/
- common.md1.8 KB
- create-pr.md3.6 KB
- default-template.md633 B
- leave-comment.md1.3 KB
- merge-pr.md3.1 KB
- read-comments.md1.4 KB
- respond-to-comment.md1.7 KB
Gives 0 of the 12 instructions most pr commit review skills give in 321 tokens
Counted across 1,055 of the 1,911 authors here whose files we hold, read 2026-09-06
- Use conventional commit message formatin 150 of 1055, across 145 files
- Announce skill usage at startin 78 of 1055
- Use imperative mood for commit descriptionsin 54 of 1055, across 51 files
- Add directory to gitignore if not ignoredin 52 of 1055, across 41 files
- Use imperative mood for commit subjectin 52 of 1055
- Run tests to verify clean baselinein 42 of 1055, across 32 files
- Push branch to originin 40 of 1055, across 38 files
- Verify worktree directory is ignored before creationin 39 of 1055, across 32 files
- Delete branches after mergingin 38 of 1055, across 30 files
- Create worktree with new branchin 37 of 1055, across 32 files
- Wrap body text at 72 charactersin 36 of 1055, across 34 files
- Auto-detect and run project setupin 35 of 1055, across 27 files
Said here and by no other author read
- Detect the platform and current branch
- Confirm write actions with a human
- Use gh or glab for operations
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.