github-pr-workflow

GitHub PR lifecycle: branch, commit, open, CI, merge.

Quality

68%

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 ./skills/github/github-pr-workflow/SKILL.md

Quality

Content

71%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 skill body is highly actionable with executable commands and a well-sequenced workflow including a CI auto-fix feedback loop. Its main weaknesses are duplicated dual-path content and reference files that exist but are not actually referenced from the body.

Suggestions

Link the existing reference files from the body (e.g. "See references/conventional-commits.md" in Section 2 and "See references/ci-troubleshooting.md" in Section 5) instead of inlining that material.

Tighten the dual gh/curl presentation — e.g. lead with gh and collapse the curl fallback into a tabbed/condensed form — and trim Section 7's repetition of earlier sections.

Add an explicit pre-merge validation checkpoint ("Verify `gh pr checks` is fully green before merging") to close the workflow_clarity gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands with little concept padding, but the dual gh/git+curl path doubles much of the content and Section 7 repeats earlier sections, so it could be noticeably tightened.	3 / 5
Actionability	Copy-paste-ready bash, curl, and inline python commands cover branch, commit, PR creation, CI monitoring, auto-fix, and merge for both auth methods, matching the fully-executable 5 anchor.	5 / 5
Workflow Clarity	A clear numbered 1–7 sequence with an explicit auto-fix feedback loop (check → fix → push → verify, capped at 3 attempts) is present, but the merge step relies only on an implicit "when green" rather than an explicit pre-merge validation checkpoint.	4 / 5
Progressive Disclosure	Bundle files references/conventional-commits.md and references/ci-troubleshooting.md exist but are never linked from the body, and their subject matter is inlined in Sections 2 and 5, matching the 3 anchor where content that should be separate is inline and references are not signaled.	3 / 5
	Total	15 / 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 specific and well-scoped to the GitHub PR lifecycle with natural trigger terms, but it omits any explicit "when to use" guidance, which caps completeness. Adding a "Use when..." clause would round it out.

Suggestions

Add an explicit trigger clause, e.g. "Use when managing GitHub pull requests — branching, committing, opening PRs, monitoring CI, or merging."

Spell out "pull request" alongside "PR" to broaden natural-term coverage.

Expand terse tokens ("branch, commit, open") into verb phrases ("create branches, make commits, open PRs") for clearer action specificity.

Dimension	Reasoning	Score
Specificity	Lists several concrete lifecycle actions ("branch, commit, open, CI, merge") covering the full PR flow, but they are terse single-word tokens rather than the explicit verb-object phrases of the 5 anchor.	4 / 5
Completeness	The description gives a clear "what" ("GitHub PR lifecycle: branch, commit, open, CI, merge") but no "Use when..." trigger clause, so completeness is capped at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	"GitHub", "PR", "CI", and "merge" are natural terms users say, but the full phrase "pull request" and common synonyms are missing, matching the 4 anchor.	4 / 5
Distinctiveness Conflict Risk	"GitHub PR lifecycle" carves a clear niche distinct from general git skills, with only minor overlap risk against the related github-code-review skill.	4 / 5
	Total	15 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: skills/github/github-pr-workflow/SKILL.md
Commit: 48f69e5

Reviewed: 2 days 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.