CtrlK
BlogDocsLog inGet started
Tessl Logo

lirantal/gh-bulk-pr-triage

Triage many open GitHub PRs at once — for each PR, check its CI verdict and mergeability, then merge (with admin bypass + squash fallback) or close, in bulk. Use when the user wants to clean up a queue of stale PRs ("close all the old Snyk PRs", "merge anything green and close anything red", "process all the dependabot PRs across my repos") spanning more than a handful of PRs. Trigger on phrases like "go through all my open PRs", "merge or close them all", "clean up the PR backlog", "any PR that's failing CI / unmergeable / stale", or when the user wants the same per-PR decision rule applied to a list of PRs. Sibling skill to `gh-bulk-repo-edit`, but the surface is PR state changes (merge / close / leave), not file contents.

75

Quality

94%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable content with executable scripts, a well-sequenced destructive-batch workflow and validation gates, and clean single-file organization. The only weakness is mild verbosity in a few anecdotal asides that could be tightened.

Suggestions

Trim the recurring 'mirrors gh-bulk-repo-edit' comparisons and the personal '76 PRs' anecdote in the Pitfalls section to recover tokens without losing the substantive warning about search substring-matching.

The two paragraphs in 'The decision tree' explaining the unmergeable bucket's social trade-offs could be condensed to the core instruction plus the two legitimate options.

DimensionReasoningScore

Conciseness

Mostly lean and free of concepts Claude already knows, but contains some chatty padding — the recurring asides comparing to gh-bulk-repo-edit and the personal anecdote about the '76 PRs' count could be trimmed.

2 / 3

Actionability

Provides copy-paste-ready, executable artifacts: a complete try_merge() fallback function, the statusCheckRollup jq query, and a full per-PR decision loop with categorical return codes.

3 / 3

Workflow Clarity

A clear Discover → Confirm → Apply sequence with explicit validation checkpoints for a destructive batch op: scope confirmation with checklist, archived-repo pre-check, continue-on-failure, and a merge-strategy retry loop.

3 / 3

Progressive Disclosure

A single self-contained SKILL.md with no bundle files and well-organized sections (decision tree, fallback chain, three-phase workflow, pitfalls, worked example); no nested references and no content that needs splitting out.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that states concrete capabilities, gives rich natural-language triggers, answers both what and when, and explicitly disambiguates from a sibling skill. No fluff or over-claims.

DimensionReasoningScore

Specificity

Enumerates multiple concrete actions — 'check its CI verdict and mergeability, then merge (with admin bypass + squash fallback) or close, in bulk' — well beyond naming only a domain.

3 / 3

Completeness

Clearly answers both what (bulk PR triage via merge/close) and when, with an explicit 'Use when...' clause and a 'Trigger on phrases like...' list.

3 / 3

Trigger Term Quality

Covers natural user phrasings extensively: 'close all the old Snyk PRs', 'merge anything green and close anything red', 'go through all my open PRs', 'clean up the PR backlog'.

3 / 3

Distinctiveness Conflict Risk

Explicitly carves a niche — 'Sibling skill to gh-bulk-repo-edit, but the surface is PR state changes (merge / close / leave), not file contents' — minimizing wrong-skill triggering.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents