CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

git-workflow

Use this skill when the user wants to automate git operations, manage branches, generate commit messages, handle PRs, set up git hooks, or implement a git workflow.

Quality

77%

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 ./skills/git-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

A well-organized, largely executable reference of git-workflow recipes with efficient token use. Its weakest point is workflow clarity: no explicit end-to-end sequence or validation checkpoints tie the individual recipes (branch, commit, PR, hooks) together.

Suggestions

Add a short ordered workflow section (e.g., 1. create branch from fresh main → 2. stage and commit → 3. rebase/squash → 4. open PR with checklist) that sequences the existing recipes end to end.

Insert validation checkpoints before risky steps, such as checking get_changed_files() output before committing and running pre-commit/tests before opening a PR.

Move the full PR checklist template and pre-commit config into a references/ file and keep only a one-line pointer in SKILL.md to trim tokens and improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean and section-driven with almost no conceptual padding, but it re-explains conventional-commit types Claude already knows and pins time-sensitive versions ("rev: v4.5.0", "24.1.1", "7.0.0") outside any 'old patterns' section — minor instances that could be trimmed.

4 / 5

Actionability

Most guidance is executable (create_branch_name, the GitPython helpers, the pre-commit YAML, the bash commands), but generate_commit_message is a pass-bodied docstring; its flexibility is explicitly justified as a guide, leaving only minor gaps versus fully copy-paste-ready.

4 / 5

Workflow Clarity

The skill reads as a collection of task recipes with no end-to-end sequence — the branch → commit → rebase → PR ordering is only implicit in the section layout, and no validation checkpoints exist (e.g., verifying staged files or passing tests before committing).

3 / 5

Progressive Disclosure

With no bundle files, the self-contained body is well organized with clear sections and a Quick Reference table for navigation, though the ~30-line inline PR checklist template is content that could live in a separate reference file.

4 / 5

Total

15

/

20

Passed

Description

75%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.

A solid description with an explicit, natural trigger clause and multiple concrete actions. Its main weaknesses are a vague "what" that only emerges implicitly from the trigger list and a few missing synonyms (pull request, merge, rebase) that users commonly say.

Suggestions

Prepend a capability statement to the description (e.g., "Automates git workflows: branch naming, commit message generation, PR checklists, merge strategies, and hook setup") so the 'what' is explicit, not just implied by the trigger list.

Add missing natural trigger terms such as "pull request", "merge", or "rebase", and drop the generic "automate git operations" / "implement a git workflow" bookends in favor of the specific actions already listed.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("manage branches, generate commit messages, handle PRs, set up git hooks"), but "automate git operations" and "implement a git workflow" are generic bookends, and merge/rebase strategies covered in the body are omitted — minor gaps in coverage rather than comprehensive.

4 / 5

Completeness

The explicit "Use this skill when the user wants to..." clause answers 'when' with concrete triggers, but the 'what' is only implicit inside the trigger list — the capability statement ("Automates git workflows...") lives in the body, not the description, so both halves are not independently and explicitly stated.

4 / 5

Trigger Term Quality

Natural user phrases like "branches", "commit messages", "PRs", and "git hooks" are present, but common variations such as "pull request", "merge", and "rebase" are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The git-workflow niche has distinct triggers (hooks, PRs, commit messages), but the broad phrase "automate git operations" creates minor overlap risk with generic git or commit-message skills.

4 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

ProwlrBot/prowlr-marketplace

Path

skills/git-workflow/SKILL.md

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.