Github Pr Creation

This automates the entire PR creation workflow with task validation baked in. It checks your commits against task docs (Spec2Ship, Kiro, Cursor rules, whatever you're using), tells you if you're missing subtasks before you even try to create the PR, runs tests, and generates a proper Conventional Commits title with populated body templates. The milestone and label logic is smart: it checks what actually exists in your repo instead of assuming defaults. Honestly, the task completion check is the killer feature here. If you're branching off feature/task-2 and only completed 2.1 and 2.2 but not 2.3, it'll catch that before you waste time on a half-baked PR. Saves you from the "oh right, I forgot that part" moment during code review.

skills.sh installs: 239
GitHub stars: 72
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add fvadicamo/dev-agent-skills --skill github-pr-creation --agent claude-code

Installs into .claude/skills of the current project.

Files

GitHub PR creation

Creates Pull Requests with task validation, test execution, and Conventional Commits formatting.

Current state

!git rev-parse --abbrev-ref HEAD 2>/dev/null !git log @{u}..HEAD --oneline 2>/dev/null || echo "(no upstream tracking)"

Core workflow

1. Confirm target branch

ALWAYS ask user before proceeding:

Creating PR from [current-branch] to [target-branch]. Correct?

Branch flow	Typical target
feature/*	develop
fix/*	develop
hotfix/*	main/master
develop	main/master

2. Search for task documentation

Look for task/spec files that describe what this PR should accomplish. Common locations by tool:

Tool/Convention	Path
Spec2Ship (s2s)	`.s2s/plans/*.md` (look for active plan matching branch name or commits)
AWS Kiro	`.kiro/specs/*/tasks.md`
Cursor	`.cursor/rules/*.md`, `.cursorrules`
Trae	`.trae/rules/*.md`
GitHub Issues	`gh issue list --assignee @me --state open`
Generic	`docs/specs/`, `specs/`, `tasks.md`, `TODO.md`