ravnhq/typescript-blueprint · Archived

github

GitHub patterns using gh CLI for pull requests, stacked PRs, code review, branching strategies, and repository automation. Use when working with GitHub PRs, merging strategies, or repository management tasks.

First seen Apr 9, 2026

Installation

$ npx skills add ravnhq/typescript-blueprint --skill github

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from ravnhq/typescript-blueprint.

npx skills add ravnhq/typescript-blueprint

Browse all from ravnhq/typescript-blueprint

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
License LICENSE
Default branch main
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseMIT
More metadata
author
Callstack
tags
github, gh-cli, pull-request, stacked-pr, squash, rebase

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,815 B
  • docs SUMMARY.md 222 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

GitHub Patterns

Tools

Use gh CLI for all GitHub operations. Prefer CLI over GitHub MCP servers for lower context usage.

Quick Commands

# Create a PR from the current branch
gh pr create --title "feat: add feature" --body "Description"

# Squash-merge a PR
gh pr merge <PR_NUMBER> --squash --title "feat: add feature (#<PR_NUMBER>)"

# View PR status and checks
gh pr status
gh pr checks <PR_NUMBER>

Stacked PR Workflow Summary

When merging a chain of stacked PRs (each targeting the previous branch):

  1. Merge the first PR into main via squash merge
  2. For each subsequent PR: rebase onto main, update base to main, then squash merge
  3. On conflicts: stop and ask the user to resolve manually
# Rebase next PR's branch onto main, excluding already-merged commits
git rebase --onto origin/main <old-base-branch> <next-branch>
git push --force-with-lease origin <next-branch>
gh pr edit <N> --base main
gh pr merge <N> --squash --title "<PR title> (#N)"

See [stacked-pr-workflow.md][stacked-pr-workflow] for full step-by-step details.

Quick Reference

File Description
[stacked-pr-workflow.md][stacked-pr-workflow] Merge stacked PRs into main as individual squash commits

Problem -> Skill Mapping

Problem Start With
Merge stacked PRs cleanly [stacked-pr-workflow.md][stacked-pr-workflow]

[stacked-pr-workflow]: references/stacked-pr-workflow.md