CtrlK
BlogDocsLog inGet started
Tessl Logo

git-advanced-workflows

Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.

83

1.09x
Quality

76%

Does it follow best practices?

Impact

96%

1.09x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/developer-essentials/skills/git-advanced-workflows/SKILL.md

The canonical home for this skill is git-advanced-workflows in wshobson/agents

SKILL.md
Quality
Evals
Security

Quality

Content

65%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 highly actionable, executable reference for advanced git operations whose main weaknesses are token efficiency (it re-teaches standard git usage Claude already knows across ~400 lines), missing embedded validation checkpoints in destructive workflows, and a progressive-disclosure structure whose referenced bundle files are entirely absent. The command examples themselves are excellent and copy-paste ready.

Suggestions

Trim or move the catalogs of standard subcommand behavior (rebase operation definitions, basic cherry-pick flags, bisect basics) into the referenced files, keeping only non-obvious guidance, decision rules (the rebase-vs-merge strategy section), and gotchas in SKILL.md.

Embed explicit validation checkpoints inside the destructive workflows (e.g., after 'git rebase -i main', add 'run tests, then git push --force-with-lease' with an abort path 'git rebase --abort' on failure) instead of listing them separately under Best Practices.

Actually provide the six referenced bundle files (references/git-rebase-guide.md, references/git-conflict-resolution.md, references/git-history-rewriting.md, assets/git-workflow-checklist.md, assets/git-aliases.md, scripts/git-clean-branches.sh) or remove the Resources section so navigation is not broken.

DimensionReasoningScore

Conciseness

The ~400-line body is command-dense with little prose padding, but much of it catalogs standard git subcommand usage Claude already knows (e.g., 'Interactive rebase is the Swiss Army knife of Git history editing', 'Your safety net - tracks all ref movements'), and the full tour of pick/reword/squash options and basic cherry-pick flags could be substantially trimmed.

3 / 5

Actionability

Every section provides copy-paste-ready executable commands ('git rebase -i HEAD~5', 'git bisect run ./test.sh', 'git push --force-with-lease origin feature/user-auth') with concrete workflows covering the common cases, including conflict resolution and abort paths.

5 / 5

Workflow Clarity

Workflows 1-5 present clear step sequences, but they involve destructive operations (force push, 'git reset --hard', history rewriting) with validation relegated to a separate Best Practices list ('Test Before Force Push') rather than embedded as explicit checkpoints, triggering the destructive-operation cap.

3 / 5

Progressive Disclosure

Section structure is good and the Resources section clearly signals six bundle files, but none of them exist in the bundle (references/, assets/, and scripts/ are absent), so the referenced navigation is broken and the inlined command tutorials are content that belongs in those separate files.

3 / 5

Total

14

/

20

Passed

Description

88%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 strong description that explicitly states both capabilities and use-when triggers with concrete, natural technique names covering the advanced git domain. Its only weaknesses are a few missing common synonyms ('lost commits', 'rewrite history', 'squash') and slightly broad collaboration triggers that create minor overlap risk with generic git skills.

DimensionReasoningScore

Specificity

It lists multiple specific concrete techniques — 'rebasing, cherry-picking, bisect, worktrees, and reflog' — with comprehensive coverage of the advanced-git domain; 'recover from any situation' is a mild over-claim but does not introduce vagueness, and unlike the 4 anchor there is no meaningful coverage gap.

5 / 5

Completeness

It explicitly answers both what ('Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation') and when ('Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues') with concrete trigger scenarios, matching the 5 anchor.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('rebasing', 'cherry-picking', 'bisect', 'worktrees', 'reflog', 'feature branches', 'troubleshooting repository issues'), but common variations users would say — 'lost commits', 'undo', 'rewrite history', 'squash' — are missing, so it falls short of the comprehensive-synonyms 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The advanced-operations niche (rebase/cherry-pick/bisect/worktree/reflog) is mostly distinct, but 'collaborating on feature branches' and 'maintain clean history' are broad enough to overlap with routine git or commit-message skills, so it does not fully meet the minimal-conflict 5 anchor.

4 / 5

Total

18

/

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

referenced_paths_exist

Referenced path issues: 6 missing

Warning

Total

15

/

16

Passed

Repository
Dicklesworthstone/pi_agent_rust
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.