Pull Request
SkillDev toolsCreate or update a pull request with a structured description.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Pull Request skill
What this skill tells your AI
The instructions your AI receives, as published by simonepri/ifttt-lint in .agents/skills/pr/SKILL.md and read by ahel’s review.
- Base: default to
main. Override with--base <branch>in $ARGUMENTS. - Preflight: check
git log <base>..HEAD --oneline. If nothing to merge, ask the user what they intended. - Push: run
git push -u origin $(git branch --show-current). If it fails because the remote has diverged (e.g., after an amend or rebase), tell the user and ask whether to force push (--force-with-lease). Never force push without confirmation. - Detect existing PR: run
gh pr view --json number,title,body 2>/dev/null. If a PR already exists, go to step 6. - Create PR:
- Gather context: read the commit messages (
git log <base>..HEAD). Run/diff <branch>for the full diff. - Write description: PRs are hierarchical — they aggregate commits.
- Single commit: the PR description is the commit message body, reformatted with markdown headings.
- Multiple commits: ask the user whether to (a) include all commits as-is, (b) squash first then PR, or (c) PR only a subset. Then aggregate the included commit messages. Add Goal/Background/Alternatives only when they provide context the individual commits don't.
- Use the same body format as
/commit(Problem + Solution with##headings). No "Test plan" or "Summary" sections. - Follow the project's PR conventions if documented (e.g., CONTRIBUTING.md).
- Title: conventional commit style, under 70 characters.
- Create a unique temp file with
mktemp /tmp/pr-body.XXXXXX.md, write the description to it, and rungh pr create --base <base> --title "<title>" -F <temp-file>.
- Gather context: read the commit messages (
- Update PR: run
/diff <branch>and compare the full diff against the current PR description. If the description no longer accurately reflects the branch's changes, create a unique temp file withmktemp /tmp/pr-body.XXXXXX.md, write the new description to it, and rungh pr edit <number> --title "<title>" -F <temp-file>.
Signals
- GitHub stars
- 26
- Last commit
- Jul 2026
Advanced
- Catalog kind
- skill
- Gateway key
pr-simonepri- Source
- github.com/simonepri/ifttt-lint