From go-workflow
Creates GitHub pull requests from current branch using repo templates, conventional commit titles, issue linking from commits/branch, and gh CLI. Invoke with $create-pr after implementation.
npx claudepluginhub gopherguides/gopher-ai --plugin go-workflowThis skill uses the workspace's default tool permissions.
Create a pull request following the repo's PR template and conventions.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Create a pull request following the repo's PR template and conventions.
$create-pr
CURRENT_BRANCH=$(git branch --show-current)
DEFAULT_BRANCH=$(git remote show origin 2>/dev/null | grep 'HEAD branch' | sed 's/.*: //')
git log "${DEFAULT_BRANCH}..HEAD" --oneline
git diff "${DEFAULT_BRANCH}..HEAD" --stat
If the current branch is main, master, or matches the default branch, stop and inform the user — do not create a PR from the default branch.
Ensure the branch is pushed to the remote:
git push -u origin "$CURRENT_BRANCH"
Check for a PR template in these locations (in order):
cat .github/pull_request_template.md 2>/dev/null || \
cat .github/PULL_REQUEST_TEMPLATE.md 2>/dev/null || \
cat docs/pull_request_template.md 2>/dev/null || \
cat pull_request_template.md 2>/dev/null || \
echo "NO_TEMPLATE"
If a template directory exists (.github/PULL_REQUEST_TEMPLATE/), list templates and ask the user which to use.
If a template was found: Use its exact section structure. Fill in every section based on the commits and diff. Do not omit or skip sections.
If no template: Use this default format:
## Summary
- <1-3 bullet points describing what changed and why>
## Test Plan
- <How the changes were tested>
Look for issue references in:
issue-42-, fix/42-)Include Fixes #<number> or Closes #<number> in the PR body.
<type>(<scope>): <subject>gh pr create --title "<title>" --body "<body>"
Display the PR URL so the user can review it.