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.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

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

A highly actionable, well-structured reference with copy-paste commands and a properly signaled one-level-deep bundle reference. Its main weaknesses are mild over-explanation of concepts Claude already knows and missing validation checkpoints on destructive operations.

Suggestions

Add explicit validation checkpoints after destructive/batch operations (e.g. after rebase or force-push: run tests / "git status" / verify CI) so workflow clarity can reach 3.

Trim explanatory one-liners that restate known concepts (e.g. the 'Binary search...', 'Swiss Army knife', and 'safety net' intros) and de-duplicate the reflog-recovery commands that appear in both the Reflog and Recovery Commands sections.

Make the pointer to references/details.md a clear inline link (e.g. [references/details.md](references/details.md)) and briefly enumerate what it contains so navigation is even more discoverable.

Dimension	Reasoning	Score
Conciseness	Code blocks are lean and copy-paste ready, but the body restates concepts Claude already knows ("Binary search through commit history to find the commit that introduced a bug", "Your safety net - tracks all ref movements") and duplicates the reflog-recovery pattern across the reflog and Recovery Commands sections.	2 / 3
Actionability	Every section provides fully executable, specific commands (e.g. "git rebase -i HEAD~5", "git cherry-pick abc123..def456", "git bisect run ./test.sh", "git worktree add -b bugfix/urgent ../project-hotfix main"), copy-paste ready with flags and ranges.	3 / 3
Workflow Clarity	Sequences exist (bisect start→bad→good→test→reset is a clear feedback loop), but destructive/batch operations like rebase, force-push, and reset --hard lack explicit post-operation validation checkpoints, which per the guidelines caps workflow clarity at 2.	2 / 3
Progressive Disclosure	The body is a clear overview with well-organized sections and a single well-signaled one-level-deep reference ("Detailed pattern documentation lives in references/details.md"), and that bundle file exists and does not nest further references.	3 / 3
	Total	10 / 12 Passed

Description

100%

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, well-scoped description that names concrete capabilities and provides an explicit trigger clause with natural terms. Minor over-claim in "recover from any situation" does not undermine its specificity or distinctiveness.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "rebasing, cherry-picking, bisect, worktrees, and reflog" — rather than vague language, matching the multiple-specific-actions anchor.	3 / 3
Completeness	Explicitly states what it does ("maintain clean history and recover from any situation") and when to use it via an explicit "Use when..." clause, satisfying both halves.	3 / 3
Trigger Term Quality	Operation names (rebasing, cherry-picking, bisect, worktrees, reflog) plus contextual triggers ("feature branches", "troubleshooting repository issues") give good coverage of terms an advanced-git user would naturally say.	3 / 3
Distinctiveness Conflict Risk	The advanced-git-workflows niche (rebase/cherry-pick/bisect/worktree/reflog) is clearly distinct from a general git skill and unlikely to trigger for the wrong skill.	3 / 3
	Total	12 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: wshobson/agents
Commit: 5cc2549

Reviewed: about 2 hours 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.