attach-review-to-pr

Add line-specific review comments to pull requests using GitHub CLI API

Quality

59%

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 ./plugins/git/skills/attach-review-to-pr/SKILL.md

Quality

Content

57%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 highly actionable with copy-paste-ready commands and thorough worked examples, but it suffers from significant redundancy and lacks a single sequenced workflow with explicit validation for its batch review-posting operation.

Suggestions

Consolidate the repeated single-comment command into one canonical example and remove the duplicated parameter table from the API Reference section.

Add one explicit end-to-end workflow (gather PR info -> check pending reviews -> post comments -> verify via the reviews endpoint) with validation checkpoints for the batch case.

Move the full API reference and parameter tables into a separate REFERENCE.md and keep SKILL.md as a concise overview pointing to it.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose: the same single-comment command is repeated across Basic Syntax, Complete Example, Common Issues, and Workflow Example 1, and the parameter tables appear twice (Parameters Explained and API Reference), constituting several padded/redundant sections rather than lean reference.	2 / 5
Actionability	Commands are fully executable and copy-paste ready, with concrete worked examples using real owner/repo/SHA values covering single comments, multi-comment reviews, multi-line comments, and error recovery for the common cases.	5 / 5
Workflow Clarity	Pre-flight checks exist (Get PR Information First, Check for Pending Reviews) and Common Issues offers error recovery, but there is no single sequenced workflow with explicit post-submission validation; since posting multi-comment reviews is a batch operation, the missing validation checkpoint caps this at 3.	3 / 5
Progressive Disclosure	The file has clear section headers and links to external docs, but the inlined ~50-line API Reference and duplicated parameter tables are content that would be better split into a separate reference file, and the only internal links (./create-pr.md, ./commit.md) point to sibling skills rather than bundle files.	3 / 5
	Total	13 / 20 Passed

Description

61%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 clear and specific about what the skill does but omits any 'when to use it' trigger guidance, which caps its completeness. It is mostly distinct from sibling skills though a few natural trigger synonyms are absent.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when adding inline review comments to a pull request or when the user asks to comment on specific lines of a PR.'

Include common trigger synonyms such as 'PR', 'inline comments', and 'code review' to improve natural-keyword coverage.

Mention both the single-comment and multi-comment review workflows in the description to broaden the action coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (PR review comments) and one concrete action ('Add line-specific review comments') plus the tool ('GitHub CLI API'), but does not enumerate multiple distinct actions, matching the anchor for 1-2 concrete actions rather than comprehensive coverage.	3 / 5
Completeness	The 'what' is clear (add line-specific review comments to PRs via gh API) but there is no 'Use when...' clause or equivalent trigger guidance, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural phrases users would say ('review comments', 'pull requests', 'line-specific') with good coverage; a few common synonyms like 'PR', 'inline comments', or 'code review' are missing, so it is not a 5.	4 / 5
Distinctiveness Conflict Risk	The niche (line-specific PR review comments via the GitHub CLI API) is fairly distinct with minor overlap risk against a generic PR-review skill; the missing trigger phrase keeps it from a 5.	4 / 5
	Total	14 / 20 Passed

Validation

75%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (512 lines); consider splitting into references/ and linking	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 2 missing	Warning

	Total	12 / 16 Passed

Repository: NeoLabHQ/context-engineering-kit
Path: plugins/git/skills/attach-review-to-pr/SKILL.md
Commit: 23e2428

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.