gentle-ai-branch-pr

Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.

Quality

72%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/branch-pr/SKILL.md

Quality

Discovery

67%

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 reasonably structured with an explicit trigger clause, which is good for completeness. However, 'Gentle AI' is unexplained jargon that reduces clarity, and the specific actions beyond 'issue-first checks' are not elaborated. The trigger terms cover the basics but miss common variations users might use.

Suggestions

Explain what 'Gentle AI' means or remove the branding term—describe the actual behavior (e.g., 'Creates pull requests that verify linked issues exist before submission').

Add more natural trigger term variations such as 'PR', 'merge request', 'submit code for review', 'open a PR'.

List additional concrete actions beyond 'issue-first checks' (e.g., 'generates PR descriptions, links related issues, validates branch readiness').

Dimension	Reasoning	Score
Specificity	Names the domain (pull requests) and mentions 'issue-first checks' as a specific action, but doesn't elaborate on what concrete steps are involved beyond that. 'Gentle AI' is unclear branding/jargon without further explanation of what it entails.	2 / 3
Completeness	Explicitly answers both 'what' (create pull requests with issue-first checks) and 'when' (trigger: creating, opening, or preparing PRs for review). The trigger clause is explicit and clearly stated.	3 / 3
Trigger Term Quality	Includes some natural terms like 'creating', 'opening', 'preparing PRs for review', and 'pull requests', but misses common variations like 'PR', 'merge request', 'code review', 'submit changes'. 'Gentle AI' is not a term users would naturally say.	2 / 3
Distinctiveness Conflict Risk	'Gentle AI' adds some distinctiveness as a brand/workflow identifier, but 'pull requests' is a broad domain that could overlap with general git workflow skills, code review skills, or CI/CD skills. The 'issue-first checks' aspect helps narrow it somewhat.	2 / 3
	Total	9 / 12 Passed

Implementation

77%

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

This is a highly actionable and well-structured skill with clear workflows, executable commands, and explicit validation checkpoints. Its main weakness is verbosity through redundancy — the same rules (400-line limit, test commands, issue linking, no Co-Authored-By) appear in Critical Rules, the workflow, the PR template, the automated checks table, and the contributor checklist. The conventional commits section and branch naming examples are thorough but could be more concise given Claude's existing knowledge.

Suggestions

Eliminate redundancy by stating each rule once in Critical Rules and referencing it elsewhere rather than repeating test commands, line limits, and issue-linking requirements across 4-5 sections.

Extract the Conventional Commits reference and PR body template into separate bundle files (e.g., COMMITS.md, PR_TEMPLATE.md) and reference them from the main skill to reduce the monolithic structure.

Trim the branch naming table to 3-4 examples since the regex pattern already communicates the full rule; Claude doesn't need 11 examples to understand the pattern.

Dimension	Reasoning	Score
Conciseness	The skill is thorough but includes significant redundancy — the PR body template, automated checks table, and contributor checklist all repeat the same information (e.g., 400-line limit, test commands, issue linking). The branch naming table with 11 examples is excessive when the regex pattern already communicates the rule. The conventional commits section is quite long and could be trimmed.	2 / 3
Actionability	Highly actionable with fully executable gh CLI commands, exact regex patterns for branch naming and commit messages, a complete copy-paste-ready PR creation command with filled-in template, and specific test commands. Every step has concrete, executable guidance.	3 / 3
Workflow Clarity	The workflow is clearly sequenced from issue verification through branch creation, implementation, testing, committing, and PR opening. Validation checkpoints are explicit — confirm issue has status:approved before starting, run tests locally before pushing, all automated checks must pass before merge. The automated checks table provides clear fix instructions for each failure mode.	3 / 3
Progressive Disclosure	The content is a monolithic document at ~200+ lines that could benefit from splitting — the conventional commits reference, PR template, and automated checks table could each be separate files. There's a reference to `.github/PULL_REQUEST_TEMPLATE.md` but the entire template is still inlined. No bundle files are provided to offload detail.	2 / 3
	Total	10 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: sergiodvillegas-art/gentle-ai
Commit: 3bfa934

Reviewed: 6 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.