GitHub PR Workflow Assistant
Manage pull requests, stacked branches, and merges through the gh CLI.
The skill exposes commands with remote repository effects, including gh operations, git rebase, force-with-lease, and squash merges, but lacks explicit stepwise user confirmation, least-privilege guidance, sensitive-data handling, rollback procedures, and data-flow disclosure. It only requires stopping for conflicts, so points are deducted.
The commands and stacked-PR workflow are broadly coherent, and conflict handling is specified. However, the workflow assumes configured authentication, existing remotes, and correct old-base branches; it lacks input validation, diagnostic failure feedback, tests, and handling for branch protection or other abnormal states. Static calibration also caps this score at 10.
The audience, scenarios, and triggers are reasonably clear for GitHub PRs, reviews, stacked PRs, and repository management. Boundaries are incomplete: it does not state GitHub CLI authentication prerequisites, non-fit cases, non-GitHub limitations, or Chinese-language considerations, so points are deducted.
The skill has clear structure, quick commands, a workflow summary, problem mapping, a linked reference, MIT licensing, and author metadata. It lacks a skill version, changelog, explicit maintenance owner and update path, FAQ, and systematic troubleshooting guidance, so it is usable but incomplete.
It can directly guide PR creation, status checks, merging, and the documented stacked-PR procedure. Still, users must supply parameters and correctly infer branch relationships; there are no verified representative outputs, and merge operations require substantial human review. The conservative static ceiling therefore limits the score.
The commands, workflow explanation, and linked local reference are auditable, and license and repository context provide limited corroboration. There is no committed test suite, CI coverage for these key paths, or third-party execution evidence, so verification remains limited.
- Before running gh pr merge, git rebase, or git push --force-with-lease, confirm the target PRs, branches, remote, protection rules, and recovery or backup plan.
- The skill does not document gh authentication, permission scope, network reachability, or detailed failure diagnosis; do not use example placeholders as real parameters.
- The stacked-PR rebase --onto procedure depends on identifying the old base branch correctly; an error can omit commits or rewrite branch history.
What does this skill do, and when should you use it?
This Callstack Agent Skill supports GitHub work performed through the GitHub CLI. It covers pull request creation, status and check inspection, code-review workflows, branching strategies, and repository management. Its most detailed workflow handles stacked pull requests by merging the lowest PR first, then rebasing, retargeting, and squash-merging each successor. When conflicts occur, it instructs the user to stop and resolve them manually.
It directs the assistant to use gh CLI for GitHub operations, including creating pull requests, viewing PR status and checks, squash-merging PRs, and editing a PR's base branch. For stacked PRs, it supplies Git commands to rebase a later branch onto main, push with force-with-lease, change the PR base to main, and squash-merge it. It also links to a stacked-pr-workflow.md reference file.
- A developer needs to create a pull request from the current branch
- A maintainer needs to inspect a PR's status or CI checks
- A team uses stacked pull requests and needs to merge them into main in order
- A maintainer needs to rebase a branch, change a PR's target branch, or perform a squash merge
What are this skill's strengths and limitations?
- Includes copyable gh CLI and Git commands
- Defines a clear order for merging stacked pull requests
- Covers PR creation, checks, merging, and base-branch updates
- Requires GitHub CLI, Git, network access, and appropriate repository permissions
- Conflict resolution is explicitly left to the user
- The SKILL.md names one stacked-PR reference file but provides no test-suite or platform-validation evidence
- The README's installation examples primarily install the broader skill collection rather than documenting a standalone copy command for this skill
How do you install this skill?
The README documents two relevant installation routes. In Claude Code, add the marketplace with /plugin marketplace add callstackincubator/agent-skills, then install /plugin install github@callstack-agent-skills. In Codex, the repository can be used through its bundled plugins. Alternatively, run git clone https://github.com/callstackincubator/agent-skills.git, then follow the README example to copy agent-skills/skills/* into .codex/skills/ or ~/.codex/skills/. The README does not document a dedicated command for copying only skills/github/.
How do you use this skill?
After the skill is recognized, give it a GitHub task involving pull requests, stacked PRs, rebasing, or repository management, such as: Create a PR from the current branch and show its checks. Documented commands include gh pr create --title "feat: add feature" --body "Description", gh pr status, and gh pr checks <PR_NUMBER>. For stacked PRs, squash-merge the first PR into main, then process each subsequent PR; stop for manual conflict resolution if needed.