CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-stack

Managing stacked/dependent pull requests with GitHub

71

2.02x
Quality

57%

Does it follow best practices?

Impact

95%

2.02x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./dot_config/opencode/skill/pr-stack/SKILL.md
SKILL.md
Quality
Evals
Security

Evaluation results

95%

95%

Setting Up a Multi-Layer Feature Branch Stack

Stack initialization and branch creation

Criteria
Without context
With context

gs repo init used

0%

100%

gs branch create for each branch

0%

100%

gs commit create for commits

0%

100%

Stack view command

0%

100%

gs ls alias mentioned

0%

100%

git stack-log alias

0%

100%

Up/down navigation

0%

100%

Top/bottom jump

0%

100%

Branch checkout command

0%

100%

gs trunk mentioned

0%

0%

100%

26%

Submitting a Feature Stack for Review

Stack submission and navigation

Criteria
Without context
With context

gs stack submit used

100%

100%

gs branch submit mentioned

100%

100%

gs downstack submit mentioned

100%

100%

gs upstack submit mentioned

100%

100%

Per-layer log command

70%

100%

Per-layer diff command

70%

100%

git stack-diff alias

0%

100%

git stack-range alias

0%

100%

Up/down navigation in guide

100%

100%

gs branch checkout in guide

100%

100%

90%

23%

Safely Merging a Stacked PR Series

Safe stack merge runbook and conflict checking

Criteria
Without context
With context

Manual detection command

60%

100%

Chain detection logic

100%

100%

Mergeability check

100%

100%

Bottom-up order

100%

100%

Squash merge with branch delete

41%

100%

gs repo sync after each merge

0%

100%

force-with-lease not force

100%

100%

CI verification step

100%

100%

Confirm before merge

100%

100%

gs log short or gs ls for stack state

0%

0%

Repository
athal7/dotfiles
Evaluated
Agent
Claude Code
Model
Claude Sonnet 4.6

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.