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

scripts/check-conflicts.sh

View on GitHub
#!/usr/bin/env bash
# Check for remaining merge conflict markers in tracked files.
#
# Usage: bash scripts/check-conflicts.sh [path...]
#
# With no args, checks all tracked files in the repo (excluding node_modules).
# With paths, checks only those files/directories.
#
# Exit code: 0 = clean, 1 = conflicts found
set -euo pipefail

if [ $# -gt 0 ]; then
  targets=("$@")
else
  # All tracked files, excluding node_modules (bash 3.2-compatible)
  targets=()
  while IFS= read -r f; do targets+=("$f"); done < <(git ls-files | grep -v node_modules)
fi

if [ ${#targets[@]} -eq 0 ]; then
  echo "✅ No files to check."
  exit 0
fi

# Search for conflict markers (must be at start of line)
matches=$(grep -Ern "^<<<<<<< |^=======$|^>>>>>>> " -- "${targets[@]}" 2>/dev/null || true)

if [ -z "$matches" ]; then
  echo "✅ No conflict markers found."
  exit 0
else
  count=$(echo "$matches" | wc -l | tr -d ' ')
  echo "❌ Found ${count} conflict marker(s):"
  echo ""
  echo "$matches"
  exit 1
fi
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