Skip to content

Add create-pull-request skill #439

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thibaudcolas merged 2 commits into from
Jun 3, 2026
Merged

Add create-pull-request skill #439

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f734cf8
Add create-pull-request skill
Raghaddahi May 31, 2026
267b818
Update SKILL.md
thibaudcolas Jun 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
49 changes: 49 additions & 0 deletions .agents/skills/create-pull-request/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,49 @@
---
name: create-pull-request
description: Steps for creating a pull request in this project.
---

## Requirements

- GitHub CLI (`gh`) installed and authenticated
- `gh pr create` — open the PR creation flow.
- `gh pr view` — verify the PR was created correctly.
- On a feature branch (not main)

## Steps

- Infer from context or ask the user if this PR fixes or relates to an issue, follow up and ask for the issue number before proceeding.
- Infer from context or ask the user to describe their AI involvement and review state:
- AI generated the code and PR description — has it been reviewed by a human?
- AI assisted with the PR description only — has it been reviewed by a human?
- Other (ask user to describe) — has it been reviewed by a human?
- Verify any needed docs and tests changes have been included.
- Run appropriate quality assurance locally before opening the PR.

## PR title guidance

- Use a descriptive title that communicates the problem solved or feature added in a few words.
- Do not use vague titles like "Fixes #123" — write "Fix documentation dark mode refresh issue (#123)" instead.

## Template

- If fully closes: Fixes #number | If related: Relates to #number
Fixes/Relates to #

### Description

- Describe the "why" of the changes. Concisely, why the proposed solution is the right one, and which other solutions might have been skipped.
- Highlight areas of the proposed changes that require careful review.
- Guidance on QA done so far vs. testing left to do.

### Testing

- Summarise results briefly, e.g. "All tests pass, no lint errors"
- Only report lint/test results for files included in this PR. Do not mention unrelated or untracked files.
- Share guidance on any specific tests related to the PR - command(s) and results.
- For frontend changes, add before/after screenshots if possible.
- Note any testing still left to do or areas needing careful review

### AI usage

- Agent: infer from your context / share user input.
Loading