pr-stack
Managing stacked/dependent pull requests with GitHub
75
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too brief and vague to effectively guide skill selection. While it identifies a specific domain (stacked PRs on GitHub), it fails to explain what concrete actions the skill performs and provides no guidance on when Claude should select it. The description reads more like a topic label than a functional skill description.
Suggestions
Add specific concrete actions like 'Creates stacked PR chains, rebases dependent branches, updates PR descriptions with stack context, manages merge order'
Add a 'Use when...' clause with trigger terms like 'Use when the user mentions PR stacks, dependent PRs, chained pull requests, rebasing PR chains, or managing multiple related PRs'
Include common term variations: 'PR', 'PRs', 'PR stack', 'branch chain', 'dependent branches'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('Managing') without listing concrete actions. It doesn't specify what managing entails - no mention of creating, rebasing, updating, merging, or any specific operations. | 1 / 3 |
Completeness | Only partially addresses 'what' (managing stacked PRs) with no detail, and completely missing 'when' - no 'Use when...' clause or explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('stacked', 'dependent', 'pull requests', 'GitHub') that users might say, but misses common variations like 'PR', 'PRs', 'PR stack', 'chained PRs', or 'branch dependencies'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'stacked/dependent pull requests' concept is somewhat specific and distinguishes it from general GitHub skills, but 'Managing' is vague enough that it could overlap with other GitHub PR-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that serves as a concise, actionable reference for managing stacked PRs. It assumes Claude's competence, provides executable commands throughout, and includes appropriate safety guardrails with validation steps. The organization is clean and the content density is high without being overwhelming.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what stacked PRs are or why they're useful. Every line is actionable reference material with commands and their purposes. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands throughout. Clear command syntax with actual flags and arguments. The git aliases and gh commands are fully executable. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced (submit flow, sync flow, merge flow). Explicit validation checkpoints included: 'Verify CI passes after each rebase', 'Check for conflicts' with specific command. Safety section provides clear guardrails. | 3 / 3 |
Progressive Disclosure | Well-organized into logical sections (Tools, Stack Operations, Manual detection, Safety). Content is appropriately sized for a single file skill. Clear headers make navigation easy without needing external references. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
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.