CtrlK
BlogDocsLog inGet started
Tessl Logo

github-pr-description

Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it matters, and how to test it.

61

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./crates/forge_repo/src/skills/github-pr-description/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 actionable and reasonably well-sequenced with a validation checkpoint, but it is token-heavy due to redundant example volume and duplicated anti-pattern lists, and it does not leverage progressive disclosure to offload the bulky examples.

Suggestions

Reduce the five full PR-description examples to two or three representative ones and move the rest into a references file.

Remove the duplicated 'What to Avoid' / 'Anti-Patterns to Avoid' lists — keep a single canonical list.

Add an explicit error-recovery step for 'gh pr create' failures (e.g., auth issues, base branch mismatches) to complete the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The body is noticeably verbose: five full worked example PR descriptions (~30 lines each) are excessive, and the 'What to Avoid' / 'Anti-Patterns to Avoid' lists are duplicated in both the Generate and Notes sections.

2 / 5

Actionability

Provides concrete, mostly executable commands (git branch/log/diff, 'gh pr create --title ... --body-file ...') and a clear write-to-temp-file step, with only minor gaps such as the templated title and narrative write-tool instruction.

4 / 5

Workflow Clarity

A clear six-step sequence with a validation checkpoint in step 1 ('If on main/master or no commits ahead, inform the user'), but lacks an error-recovery feedback loop for the gh pr create step.

4 / 5

Progressive Disclosure

Sections are well organized, but the skill is a 350-line monolith with no bundle files; the five long examples and reference-style guidance are inlined rather than split into a separate references file.

3 / 5

Total

13

/

20

Passed

Description

87%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 strong: it clearly states both capability and trigger conditions with concrete, natural-language phrases and a well-scoped niche. Minor redundancy in action phrasing and a few missing synonyms prevent a perfect specificity/trigger score.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Generate and create pull request descriptions', 'Analyzes git diff and commit history', 'explain what changed, why it matters, and how to test it'), though the create/generate phrasing is somewhat redundant, keeping it just below comprehensive.

4 / 5

Completeness

Explicitly states what it does ('Generate and create pull request descriptions automatically using GitHub CLI') and when to use it via a concrete 'Use when...' clause with multiple trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases ('create a PR', 'generate a PR description', 'make a pull request', 'submit changes for review'), but misses common synonyms like 'open a PR'.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (PR description generation via GitHub CLI) with distinct triggers, giving minimal overlap risk with other skills.

5 / 5

Total

18

/

20

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.

Repository
tailcallhq/forgecode
Reviewed

Table of Contents

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.