// Opens a GitHub Pull Request from the current branch, linking it to the related issue when the branch name starts with an issue number.
| name | create-pull-request |
| description | Opens a GitHub Pull Request from the current branch, linking it to the related issue when the branch name starts with an issue number. |
Use this skill when asked to open, create, or submit a Pull Request (PR) for the current branch.
npm run lint
npm run check
Fix any errors before continuing.
git push -u origin $(git branch --show-current)
Check the current branch name to determine whether it is linked to a GitHub issue:
git branch --show-current
If the branch name starts with a number followed by a hyphen (e.g. 42-add-dark-mode-toggle), extract the issue number:
BRANCH=$(git branch --show-current)
ISSUE=$(echo "$BRANCH" | grep -oP '^\d+')
echo $ISSUE # prints the issue number, or nothing if not an issue branch
$ISSUE is non-empty → the PR must be linked to that issue (see step 5).$ISSUE is empty → no automatic issue link is required.Title — follow Conventional Commits style, concise and descriptive:
feat: add dark mode toggle
fix: header overlaps on mobile
docs: update contributor guide
chore: upgrade SvelteKit to v2
Body template:
## Summary
<!-- What does this PR do? One or two sentences. -->
## Changes
## <!-- Bullet list of notable changes -->
-
## Related issue
Closes #<issue-number>
## Checklist
- [ ] `npm run lint` passes
- [ ] `npm run check` passes
- [ ] Manually tested in the browser (if UI changes)
If the branch is not linked to an issue, omit the "Related issue" section entirely.
gh pr create \
--base develop \
--title "<PR title>" \
--body "$(cat <<'EOF'
## Summary
<summary>
## Changes
- <change 1>
- <change 2>
Closes #<issue-number>
EOF
)"
Or open the GitHub web UI directly:
gh pr create --web
The default target branch for this project is
develop, notmain.
After the PR is created:
Closes #<issue-number> to the PR description — GitHub picks this up automatically.Accepted closing keywords: Closes, Fixes, Resolves (case-insensitive).
npm run lint and npm run check passdevelopCloses #<issue-number> when branch starts with an issue numberCreates a new blog post for the Torrust website. Use when asked to write, add, create, or publish a new blog post or article.
Creates a new git branch for a GitHub issue following naming conventions with issue number as prefix.
Creates a new Svelte UI component for the Torrust website. Use when asked to add, create, or build a new reusable UI component, widget, or UI element.
Deploys the Torrust website to GitHub Pages. Use when asked to deploy, publish, or release the site, or to set up the deployment workflow.
Runs the full quality check suite for the Torrust website. Use before committing or opening a PR to verify types, linting, and that the build succeeds.
Updates the contributors list on the Torrust website homepage. Use when asked to refresh, update, or sync the contributors list from the Torrust GitHub org.