Skip to content

espennilsen/pi / skills/github

github

Verified

Interact with GitHub repos, PRs, issues, CI, and notifications via the pi-github extension commands and gh CLI. Use when asked to check PRs, list issues, view repo status, check CI, browse notifications, create or merge PRs, fix PR review feedback, or perform any GitHub operation. **Triggers:** "open PRs", "repo status", "CI status", "merge PR", "fix PR", "fix PRs", "fix review feedback", "create PR", "GitHub notifications", any /gh-* command, or when a GitHub PR URL is shared.

FileKindSize
SKILL.mdskill md4.0 KB
references/pr-create.mdmarkdown1.2 KB
references/pr-fix-parallel.mdmarkdown7.8 KB
references/pr-fix.mdmarkdown4.8 KB
references/pr-merge.mdmarkdown2.9 KB
scripts/check-conflicts.shexecutablescript997 B
scripts/fetch-threads.shexecutablescript2.7 KB
scripts/reply-thread.shexecutablescript1.1 KB
scripts/resolve-thread.shexecutablescript1.2 KB

references/pr-create.md

View on GitHub
# PR Create — Create PR with Generated Summary

Create a pull request with an LLM-generated title and description.

## Quick Path

```
/gh-pr-create [base-branch]
```

Default base: `main`. Must be on a feature branch (not main/master).

The command:

1. Checks no PR already exists for the branch
2. Pushes the branch to origin
3. Gathers commits, diff stat, and full diff
4. Sends context to the LLM as a follow-up message
5. LLM drafts a title and description
6. **Presents the draft to the user for review before creating**
7. Creates the PR via `gh pr create`

## Manual Workflow

```bash
# Push the branch
git push -u origin <branch>

# Gather context
git log main..<branch> --pretty=format:"%h %s" --reverse
git diff main...<branch> --stat
git diff main...<branch>

# Create PR
gh pr create --base main --title "..." --body "..."
```

## PR Description Guidelines

- Start with a concise summary of what and why
- List key changes as bullet points
- Keep it factual — no filler
- Call out breaking changes explicitly
- Use markdown formatting

## Conventions

- Always push before creating the PR
- Check for existing PRs on the branch first
- Present draft to user before running `gh pr create`
- Truncate diff at 50KB if too large
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 319kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 319kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 319kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 319kUpdated Claude CodeCodexVerifiedInstall