CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

semantic-szz-analyzer

Identify bug-introducing commits using semantic analysis that extends traditional SZZ algorithm. Distinguishes semantic changes from refactorings or code movements using control-flow and data-flow similarity analysis. Use when analyzing bug-fix commits to trace back to bug-introducing changes, investigating software evolution, conducting empirical studies on defect prediction, or reducing false positives in bug localization. Supports git repositories and provides explanations for why commits are identified as bug-introducing.

Quality

80%

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 ./skills/semantic-szz-analyzer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 is well-structured with executable commands and properly bundled, verifiable references. Its main weaknesses are redundant content between the Overview, Core Capabilities, and Workflow sections, and a total absence of validation/verification steps for batch and candidate-ranking operations, which caps workflow clarity.

Suggestions

Merge the 'Core Capabilities' section into the Workflow (or cut it) — the Overview, Capabilities, and Workflow currently cover the same three ideas twice, costing tokens without adding guidance.

Add validation checkpoints to the workflow: after Step 2 confirm candidate commits were found before running semantic analysis, and after batch analysis verify the JSON report is well-formed and contains expected fields.

Specify the --fixes-file input format for batch_analyze.py and move the full JSON output schema and language-parser comparison into references/ to slim the main body.

DimensionReasoningScore

Conciseness

The Overview restates the frontmatter description almost verbatim, and the 'Core Capabilities' sections (semantic change detection, bug-introducing identification, false-positive reduction) substantially duplicate the five-step Workflow that follows — e.g., 'git blame' tracing appears in both. Mostly efficient but with unnecessary repetition that could be tightened; not 4 because the duplication is more than a minor instance.

3 / 5

Actionability

Provides concrete, executable commands throughout — 'git blame -L <start>,<end> <file> <bug-fix-commit>^', 'python scripts/semantic_szz.py --repo /path/to/repo --fix-commit abc123 --output report.json --explain' — all referencing scripts that exist in the bundle, plus a complete JSON output example. Not 5: the --fixes-file format for batch analysis and threshold-override usage are unspecified, leaving small gaps.

4 / 5

Workflow Clarity

The five-step workflow is clearly sequenced with specific commands, but there are no validation or verification checkpoints anywhere — e.g., nothing confirms candidates were actually found or that batch output is well-formed. Per the rubric, batch operations (batch_analyze.py over a fixes file) without validation steps cap workflow clarity at 3 even though the sequence itself would rate 4-5.

3 / 5

Progressive Disclosure

Well-organized body with one-level-deep, clearly signaled references — inline ('See [references/language_support.md](references/language_support.md) for details') and in a dedicated References section — and all six referenced bundle files (3 references, 3 scripts) exist. Not 5: minor gaps — the inline language-parser list and full JSON output schema could live in references, and the dual inline-plus-References linking is slightly redundant.

4 / 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 with concrete, third-person capability statements and an explicit multi-trigger 'Use when' clause. Trigger coverage is good but lacks a few natural phrasings, and a couple of broad use cases slightly raise conflict risk.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'Identify bug-introducing commits', 'Distinguishes semantic changes from refactorings or code movements using control-flow and data-flow similarity analysis', and 'provides explanations for why commits are identified as bug-introducing' — with comprehensive coverage of the skill's capabilities. Not 4: there are no meaningful gaps; the actions are concrete and exhaustive for this niche.

5 / 5

Completeness

Clearly answers both 'what' (identify bug-introducing commits, distinguish semantic changes from refactorings, provide explanations) and 'when' with an explicit 'Use when analyzing bug-fix commits... investigating software evolution, conducting empirical studies on defect prediction, or reducing false positives in bug localization' clause containing concrete trigger phrases. Not 4: the 'when' is explicit and specific, not merely present.

5 / 5

Trigger Term Quality

Good natural keyword coverage including 'bug-fix commits', 'defect prediction', 'bug localization', 'git repositories', and 'false positives' — terms the target user would say. Not 5: misses common variations like 'find the commit that introduced the bug', 'git blame', or 'regression'.

4 / 5

Distinctiveness Conflict Risk

Clear niche (semantic SZZ bug-introducing commit analysis) with distinct technical triggers unlikely to fire for unrelated skills. Not 5: the broader triggers 'investigating software evolution' and 'conducting empirical studies' create minor overlap risk with general code-analysis or git-history skills.

4 / 5

Total

18

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

ArabelaTso/Skills-4-SE

Path

skills/semantic-szz-analyzer/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.