CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

git-pr-workflows-git-workflow

Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern g

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/git-pr-workflows-git-workflow/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 body delivers a genuinely well-sequenced five-phase workflow with concrete role prompts and honest safety/authority framing, but it is padded with repeated dispatch boilerplate and filler sections, and it inlines ten prompt templates that belong in a reference file. Adding explicit failure-handling loops and the missing git/gh commands would round it out.

Suggestions

State the agent-dispatch rule once in 'Supported execution and authority' and delete the ten per-phase repetitions ('Perform this role directly, or assign it through an available permitted agent tool...').

Remove the '[Extended thinking:]' paragraph and the generic Instructions filler; replace with the actual command sequences for branch creation, commit, push, and 'gh pr create'.

Move the ten role-prompt templates to references/prompts.md and keep a one-line summary per phase in SKILL.md; add explicit feedback loops (e.g., 'if critical issues are found, fix and re-run the review before proceeding').

DimensionReasoningScore

Conciseness

The same dispatch sentence ('Perform this role directly, or assign it through an available permitted agent tool using the role prompt below') is repeated ten times across phases, an '[Extended thinking:]' paragraph explains the well-known rationale for multi-agent QA, and the Instructions section is generic filler ('Apply relevant best practices and validate outcomes') — several padded sections that could be collapsed.

2 / 5

Actionability

Role prompts are copy-paste ready with defined JSON output formats, and concrete commands appear ('git revert <commit-hash>', 'gh pr merge <number> --merge --repo ...'), but the core flow lacks the actual commands for branch creation, committing, pushing, and 'gh pr create', leaving minor gaps.

4 / 5

Workflow Clarity

Five phases are clearly sequenced with context passing ('Context from previous'), expected outputs, a pre-push validation phase, success criteria, and rollback procedures; however, there are no explicit feedback loops for error recovery (e.g., what to do when tests fail or review finds critical issues).

4 / 5

Progressive Disclosure

Section headers are clear, but ~80 lines of role-prompt templates belong in a separate references file, and the skill ships no bundle files at all despite being 145 lines — content that should be separate is inline.

3 / 5

Total

13

/

20

Passed

Description

57%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 communicates a clear pipeline concept with some natural trigger terms, but it is truncated mid-sentence, padded with orchestration buzzwords, and entirely missing 'when to use' guidance. It reads as an unfinished draft of what could be a solid description.

Suggestions

Complete the truncated text ('This workflow implements modern g') and drop buzzword framing like 'comprehensive' and 'leveraging specialized agents' in favor of concrete actions (e.g., 'reviews diffs, runs tests, generates Conventional Commits messages, creates PRs').

Add an explicit trigger clause, e.g., 'Use when the user asks to review, commit, and open a pull request for their changes end-to-end.'

Add natural trigger variations such as 'pull request', 'commit message', and 'branch' to improve trigger term coverage and distinguish it from single-purpose commit-message or PR skills.

DimensionReasoningScore

Specificity

The description names the domain ('git workflow from code review through PR creation') and several activities ('quality assurance, testing, and deployment readiness'), but the framing leans on buzzwords ('comprehensive', 'leveraging specialized agents') and the text is truncated mid-word ('This workflow implements modern g'), leaving the action list incomplete rather than comprehensive.

3 / 5

Completeness

The 'what' is stated clearly (orchestrate review-through-PR pipeline) but there is no 'Use when...' clause or equivalent trigger guidance, and the description is cut off mid-sentence, capping completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

It includes natural phrases users would say such as 'git workflow', 'code review', 'PR creation', and 'testing', matching the 'good keyword coverage' anchor; common variations like 'pull request' and 'commit message' are missing, keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

The pipeline scope (review, testing, commits, push, PR) is somewhat specific but overlaps with dedicated commit-message, code-review, and PR-creation skills, fitting the 'could still overlap with similar skills' anchor.

3 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/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.