pr-ready

Resolve CI failures, merge conflicts, or local branch changes to get a PR ready

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/pr-ready/SKILL.md

Quality

Content

86%Weight 40%Scale 1-5

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

The content is a concise, well-organized procedural skill with explicit validation checkpoints for its destructive/batch operations. Adding exact gh command syntax and a final push-verification step would make it fully copy-paste ready.

Suggestions

Provide concrete `gh` command examples, e.g. `gh pr checks` and `gh pr view`, instead of referring to the CLI generically.

Add an explicit verification step after resolving merge conflicts (e.g. 'run the full test suite before pushing').

Spell out the pre-push confirmation trigger, e.g. 'Pause and ask the user before running `git push`.'

Dimension	Reasoning	Score
Conciseness	The body is lean and scenario-driven with no padding or explanation of concepts Claude already knows; every line earns its place.	5 / 5
Actionability	It names concrete tools (`git status`, `gh` CLI) and clear per-scenario steps, but stops short of exact command syntax (e.g. the specific `gh pr checks` invocation), leaving minor gaps.	4 / 5
Workflow Clarity	Each scenario is a clearly numbered sequence with explicit validation checkpoints (run local checks, ask before pushing), though the merge-conflict path lacks a final verification step before pushing.	4 / 5
Progressive Disclosure	Under 50 lines, single-purpose, and cleanly organized by scenario with no bundle files needed; the simple-skill exception applies.	5 / 5
	Total	18 / 20 Passed

Description

66%Weight 40%Scale 1-5

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

The description is concrete and distinct, clearly naming three PR-readiness scenarios, but it omits an explicit "Use when..." trigger clause, which caps its completeness. Adding trigger phrases would lift it into the top band.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when a PR has failing CI, merge conflicts, or unpushed local changes.'

Include natural synonyms users might say, such as 'failing checks', 'red CI', or 'out-of-date branch'.

Consider naming the final action explicitly (e.g. 'push the branch and confirm checks pass') to round out the action list.

Dimension	Reasoning	Score
Specificity	"Resolve CI failures, merge conflicts, or local branch changes" names three concrete action domains, with only minor coverage gaps (e.g., no mention of pushing).	4 / 5
Completeness	It clearly states what the skill does but lacks any "Use when..." trigger clause, which the guideline caps at 3.	3 / 5
Trigger Term Quality	"CI failures", "merge conflicts", "local branch changes", and "PR" are natural terms users say, though a few common synonyms (e.g. "red CI", "failing checks") are absent.	4 / 5
Distinctiveness Conflict Risk	The PR-readiness niche is distinct with clear triggers; only minor overlap risk with general git skills.	4 / 5
	Total	15 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: remotion-dev/remotion
Path: .agents/skills/pr-ready/SKILL.md
Commit: 77354de

Reviewed: about 19 hours ago

Table of Contents

Discovery Implementation Validation

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.