pr-lifecycle

Complete issue → PR → merge lifecycle with readiness checks

Quality

63%

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 ./.copilot/skills/pr-lifecycle/SKILL.md

Quality

Content

77%

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

The body is a strong, highly actionable operational playbook with excellent workflow sequencing and validation, but it is long and monolithic — it would benefit from moving the design-doc-style gap analysis into a reference file.

Suggestions

Move the 'Readiness Check Gaps & Recommendations' section (with its JavaScript implementations and integration notes) into a separate reference file and link to it from the body.

Consider splitting the 11 readiness-check tables into a references/ file so SKILL.md stays a lean overview with the procedure and gotchas.

Tighten the check tables by collapsing the repeated What/Pass/Fix/Gotcha boilerplate where the fix command already implies the pass condition.

Dimension	Reasoning	Score
Conciseness	Most content is repo-specific actionable detail rather than concepts Claude already knows, but the ~120-line 'Readiness Check Gaps & Recommendations' section with full JavaScript implementations is design-doc material that pads the skill and could be tightened or split out.	2 / 3
Actionability	The body provides fully executable git/gh commands, exact PR title and body templates, branch-naming format, and changeset format — copy-paste ready and matching the level-3 anchor.	3 / 3
Workflow Clarity	A clear six-phase sequence carries explicit validation checkpoints (pre-push diff checks, build/test/lint, the 11 readiness gates) and feedback loops (rebase→resolve→force-with-lease, CI rerun), with an anti-patterns checklist.	3 / 3
Progressive Disclosure	The skill is internally well-sectioned and signals cross-skill references in the Scope section, but it is monolithic at ~530 lines with no bundle files; content that should be separate (the gap analysis and JS implementations) is inlined.	2 / 3
	Total	10 / 12 Passed

Description

50%

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 conveys the skill's purpose compactly but is uniformly middling: it answers 'what' without an explicit 'when' trigger and uses compressed phase notation rather than concrete, distinctive actions.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when picking up a GitHub issue and carrying it through to a merged PR in the Squad repo'.

Expand the action list into concrete verbs (e.g. 'pick up issues, create branches, run readiness checks, open and merge PRs') instead of flow-arrow shorthand.

Tie the description to the Squad repo specifically to reduce overlap with generic git/PR workflow skills.

Dimension	Reasoning	Score
Specificity	The phrase "Complete issue → PR → merge lifecycle with readiness checks" names the domain and phases, but compresses them into flow-arrow notation rather than listing multiple distinct concrete actions as the level-3 anchor requires.	2 / 3
Completeness	It clearly states what the skill does (issue→PR→merge lifecycle) but gives no explicit "when to use it" guidance; per the rubric a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like "issue", "PR", and "merge" are natural, but there is no "Use when..." trigger clause and common variations (e.g., pull request, code review, CI) are missing, matching the level-2 anchor.	2 / 3
Distinctiveness Conflict Risk	It has a recognizable niche, but "PR" and "merge" are generic enough to overlap with a general git-workflow skill, so it is not yet a level-3 clear niche.	2 / 3
	Total	8 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (538 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: bradygaster/squad
Path: .copilot/skills/pr-lifecycle/SKILL.md
Commit: e23dd92

Reviewed: 1 day 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.