CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

git-pr-workflows-git-workflow

Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.

Quality

74%

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

Quality

Content

60%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 body presents a well-sequenced five-phase orchestration with clear roles, prompts, and expected outputs per step, and includes validation phases and success criteria. Its main weaknesses are padding (a leaked extended-thinking block and generic filler sections), placeholder-only guidance with almost no executable commands, and missing error-recovery loops.

Suggestions

Delete the "[Extended thinking: ...]" block, the generic Instructions bullets, and the boilerplate Use/Do-not-use sections — they add tokens without actionable guidance.

Add the actual executable commands for the core operations (e.g. `git checkout -b`, `git commit`, `git push`, `gh pr create`) instead of relying solely on [insert ...] prompt templates.

Add explicit error-recovery loops (e.g. "if pre-push validation reports blocking issues, return to Phase 1 with the issue list") and consider moving Best Practices and Rollback Procedures to a references file.

DimensionReasoningScore

Conciseness

The phase prompts are dense and substantive, but the "[Extended thinking: ...]" meta-commentary block, the generic Instructions bullets ("Clarify goals, constraints, and required inputs"), and the boilerplate use/do-not-use sections are unnecessary padding that could be cut.

3 / 5

Actionability

Subagent prompts are detailed templates with JSON output formats, but nearly all content is fill-in placeholders ("[insert branch]", "[insert file list and summary]") and only one real command (`git revert <commit-hash>`) appears — no executable git/gh commands for committing, pushing, or creating the PR.

3 / 5

Workflow Clarity

Five clearly sequenced phases with per-step expected outputs, explicit context passing, pre-push validation, and a Success Criteria checklist; however, error-recovery loops are thin — pre-push "blocking issues" have no loop-back path — so it falls short of the anchor-5 feedback-loop standard.

4 / 5

Progressive Disclosure

A single-file skill with no bundle, well-sectioned by phases and clear headers, and easy to navigate; the minor gap is that the long prompt templates, Best Practices Reference, and Rollback sections could be externalized to keep SKILL.md leaner.

4 / 5

Total

14

/

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 that names four concrete workflow stages and includes an explicit Use-when clause in third-person imperative voice. It falls short of top marks because the trigger phrasing is abstract process language and lacks natural synonyms like "PR", "code review", or "branch".

Suggestions

Rewrite the when-clause with concrete trigger phrases users would naturally say, e.g. "Use when the user wants to commit changes, open a PR, or run a full pre-PR check on a branch".

Add natural synonyms such as "PR", "code review", and "branch" to broaden trigger coverage without adding length.

DimensionReasoningScore

Specificity

"code checks, testing, commits, and pull request preparation" lists four specific actions in the git domain, but "code checks" is generic compared to the fully concrete verbs in the anchor-5 example, so minor gaps remain.

4 / 5

Completeness

Both a clear what ("Guide changes through code checks, testing, commits, and pull request preparation") and an explicit "Use when..." clause are present, but the when-clause is process-speak ("verifying readiness for collaboration") rather than concrete user trigger phrases.

4 / 5

Trigger Term Quality

Natural terms like "Git workflow", "commits", "pull request", and "testing" are present, but common synonyms users would say ("PR", "code review", "branch", "push") are missing, matching the good-coverage-with-a-few-gaps anchor.

4 / 5

Distinctiveness Conflict Risk

The "complete Git workflow" end-to-end framing carves a clear niche, though "commits" and "code checks" create minor overlap risk with narrower commit-message or code-review 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

rmyndharis/antigravity-skills

Path

skills/git-pr-workflows-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.