bisect-aware-instrumentation

Instrument code to support efficient git bisect by producing deterministic pass/fail signals and concise runtime summaries for each tested commit. Use when debugging regressions with git bisect, automating bisect workflows, creating bisect test scripts, handling flaky tests during bisection, or needing clear exit codes and logging for automated bisect runs. Helps identify the exact commit that introduced a bug through automated testing.

1.30x

Quality

92%

Does it follow best practices?

Impact

86%

1.30x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

85%

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

This is a strong skill with excellent actionability and workflow clarity. The code examples are executable and comprehensive, covering multiple use cases from simple test bisection to performance regression detection. The main weakness is some verbosity in explanatory sections that could be trimmed, as Claude already understands git bisect basics and exit code conventions.

Suggestions

Remove or significantly condense the 'Understand the Regression' section - Claude knows how to clarify requirements without being told to ask these questions

Trim the exit code convention explanation to just the table/list format without the explanatory text

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some unnecessary explanation (e.g., explaining what exit codes mean when Claude knows this, the overview section restating the description). Some sections like 'Understand the Regression' explain concepts Claude already knows.	2 / 3
Actionability	Excellent executable code examples throughout - all bash scripts are copy-paste ready with proper exit codes, error handling, and real commands. The patterns section provides concrete, working templates for different use cases.	3 / 3
Workflow Clarity	Clear 5-step workflow with explicit validation checkpoints. The scripts include proper error handling, retry logic for flaky tests, and the troubleshooting section addresses common failure modes with specific solutions.	3 / 3
Progressive Disclosure	Well-structured with clear sections progressing from core workflow to patterns to advanced techniques. References to external files (references/git_bisect_guide.md, scripts/bisect_template.sh) are one level deep and clearly signaled at the end.	3 / 3
	Total	11 / 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.

This is an excellent skill description that hits all the marks. It provides specific concrete actions, includes comprehensive natural trigger terms that developers would use, explicitly states both what the skill does and when to use it with a clear 'Use when' clause, and occupies a distinct niche around git bisect automation that won't conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Instrument code', 'producing deterministic pass/fail signals', 'concise runtime summaries', 'creating bisect test scripts', 'handling flaky tests'. These are concrete, actionable capabilities.	3 / 3
Completeness	Clearly answers both what ('Instrument code to support efficient git bisect by producing deterministic pass/fail signals...') and when ('Use when debugging regressions with git bisect, automating bisect workflows...'). Has explicit 'Use when' clause with multiple trigger scenarios.	3 / 3
Trigger Term Quality	Excellent coverage of natural terms: 'git bisect', 'debugging regressions', 'bisect workflows', 'bisect test scripts', 'flaky tests', 'exit codes', 'automated bisect runs'. These are terms developers would naturally use when needing this skill.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive niche focused specifically on git bisect workflows. The combination of 'git bisect', 'deterministic pass/fail signals', and 'bisect test scripts' creates a clear, unique domain unlikely to conflict with general git or testing skills.	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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ArabelaTso/Skills-4-SE
Commit: 0f00a4f

Reviewed: 4 months 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.