git-bisect-assistant
Automatically performs git bisect to identify the first bad commit that introduced a bug or failure. Use when debugging regressions, tracking down when a test started failing, or identifying which commit broke functionality. Handles flaky tests with retry logic and provides comprehensive reports with bisect logs and confidence levels.
Install with Tessl CLI
npx tessl i github:ArabelaTso/Skills-4-SE --skill git-bisect-assistant83
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
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 clearly articulates specific capabilities (git bisect automation, flaky test handling, comprehensive reporting), provides explicit trigger conditions with natural user language, and occupies a distinct niche. The description follows third person voice and balances conciseness with completeness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'performs git bisect', 'identify the first bad commit', 'handles flaky tests with retry logic', 'provides comprehensive reports with bisect logs and confidence levels'. | 3 / 3 |
Completeness | Clearly answers both what ('performs git bisect to identify bad commits, handles flaky tests, provides reports') AND when ('Use when debugging regressions, tracking down when a test started failing, or identifying which commit broke functionality'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'git bisect', 'bug', 'failure', 'regressions', 'test started failing', 'commit broke functionality', 'flaky tests'. Good coverage of terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on git bisect automation with distinct triggers like 'bisect', 'first bad commit', 'regressions'. Unlikely to conflict with general git or testing skills due to specific bisect focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent concrete examples and clear command patterns. The main weaknesses are some verbosity in explaining concepts Claude already knows (exit codes, basic git concepts) and missing explicit validation steps in the workflow for error recovery during the bisect process.
Suggestions
Add explicit validation steps to the workflow, such as 'Verify bisect completed: check for exit code 0 and presence of First Bad Commit in output'
Remove or condense the 'Test Command Guidelines' section - Claude understands exit codes and test determinism
Consider moving the 'Common Scenarios' and 'Troubleshooting' sections to a separate EXAMPLES.md or TROUBLESHOOTING.md file with clear references
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy - the 'Test Command Guidelines' section explains exit codes which Claude already understands, and the 'Tips' section contains some obvious advice. The scenarios section adds value but could be more compact. | 2 / 3 |
Actionability | Provides fully executable commands with concrete examples throughout. The quick start, scenarios, and test command examples are all copy-paste ready with real command patterns and specific flags. | 3 / 3 |
Workflow Clarity | The workflow section lists steps but lacks explicit validation checkpoints. There's no guidance on verifying the bisect completed successfully or handling cases where the script fails mid-process. The troubleshooting section helps but doesn't integrate into the workflow as validation steps. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The detailed scenarios, troubleshooting, and tips could be split into separate reference files. For a skill of this length (~150 lines), some content could be externalized. | 2 / 3 |
Total | 9 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.