Create Pull Request
SkillDev toolsCreate a pull request with full validation. Use when ready to submit work for review.
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 Create Pull Request skill
What this skill tells your AI
The instructions your AI receives, as published by stevegjones/ai-first-sdlc-practices in skills/pr/SKILL.md and read by ahel’s review.
Run full validation, then create a PR if clean.
Steps
- Run pre-push validation
/sdlc-core:validate --pre-push
-
If validation fails, report the issues and stop. Do NOT push or create PR.
-
Re-verify any test counts cited in the PR body.
--pre-pushruns the pytest suite only. If the draft PR body cites results from integration smokes, E2E suites, soak tests, container tests, or any other harness outsidelocal-validation.py, re-run those exact suites in this session and update the counts in the body to match the fresh run.Example: a PR body saying "266 unit tests, 20/20 container smoke, 8/8 sequential E2E, 18/18 fresh-user-flow" requires
pytest tests/ -q,bash tests/integration/workforce-smoke/run-containers.sh,bash tests/integration/workforce-smoke/run-e2e.sh, andbash tests/integration/workforce-smoke/run-fresh-user-flow.shto all run this session before the PR is opened.Session memory of test counts goes stale fast — fixtures grow, assertions drift, environments change. Only numbers you have just observed this session belong in the body. If a suite cannot run in this environment (missing binary, no Docker, etc.), delete the number from the body and say so explicitly rather than leaving a stale figure that cites another machine's result.
If the PR already exists and counts have drifted post-creation, update the body in place rather than closing and recreating:
gh pr edit <number> --body-file <updated-body.md> -
Verify required artifacts exist:
- Feature proposal in
docs/feature-proposals/ - Retrospective in
retrospectives/ - If either is missing, warn the user and ask whether to proceed.
- Feature proposal in
-
If validation passes, proceed:
- Check if the branch tracks a remote:
git branch -vv - Push to remote with tracking:
git push -u origin <branch> - Base branch defaults to
mainunless$ARGUMENTSspecifies otherwise
- Check if the branch tracks a remote:
-
Create the PR using
gh pr create:
gh pr create --title "<short title under 70 chars>" --body "$(cat <<'EOF'
## Summary
<1-3 bullet points summarizing the changes>
## Changes
<List of files modified/created>
## Test plan
- [ ] `/sdlc-core:validate --pre-push` passes
- [ ] CI pipeline passes
<additional test steps as needed>
🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"
- Report the PR URL to the user.
Signals
- GitHub stars
- 41
- Forks
- 6
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
pr-stevegjones- Source
- github.com/stevegjones/ai-first-sdlc-practices