gitnexus-impact-analysis

Analyze blast radius before making code changes

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./gitnexus-cursor-integration/skills/gitnexus-impact-analysis/SKILL.md

Quality

Content

92%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 content is highly actionable and well-sequenced with concrete commands, fallbacks, and recovery loops; its only weakness is mild redundancy across the workflow, checklist, and example.

Dimension	Reasoning	Score
Conciseness	The body is lean with compact tables and no padding of concepts Claude already knows, though the impact→READ→detect→risk flow is restated across the workflow, checklist, and example and could be trimmed.	4 / 5
Actionability	MCP calls are given with full parameters plus executable CLI fallback commands and a worked validateUser example, making the guidance copy-paste ready across common cases.	5 / 5
Workflow Clarity	A numbered workflow pairs with a checklist, an explicit recovery loop ("If Index is stale → run analyze"), and a detect_changes pre-commit verification checkpoint, plus a risk-assessment table.	5 / 5
Progressive Disclosure	This short single-purpose skill is organized into clearly signaled sections with one one-level-deep reference (gitnexus://repo/{name}/processes) and no bundle files, satisfying the simple-skill exception.	5 / 5
	Total	19 / 20 Passed

Description

53%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.

The description is clear and distinct but terse: it names one action and one trigger without synonyms or explicit "Use when" guidance, capping several dimensions at 3.

Suggestions

Add an explicit "Use when..." clause with concrete trigger phrases (e.g., "Use when changing shared functions, before commits, or when asked 'what will break?'").

Broaden trigger term coverage with synonyms like "impact analysis", "dependents", and "callers" so it matches more natural phrasings.

List 1-2 more concrete actions (e.g., "find dependents, detect changed symbols, assess risk") to lift specificity.

Dimension	Reasoning	Score
Specificity	"Analyze blast radius" names the domain and a concrete action but stops at one verb with a vague outcome, matching the anchor that lists 1-2 actions without comprehensive coverage.	3 / 5
Completeness	It states a clear "what" (analyze blast radius) and a weakly implied "when" (before code changes) but lacks an explicit "Use when..." clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	"blast radius" is a natural phrase users would say, but synonyms like "impact analysis", "dependents", or "callers" are absent, leaving common variations missing.	3 / 5
Distinctiveness Conflict Risk	"blast radius before making code changes" carves a mostly-distinct niche (impact analysis) with only minor overlap risk against general coding aids.	4 / 5
	Total	13 / 20 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: abhigyanpatwari/GitNexus
Path: gitnexus-cursor-integration/skills/gitnexus-impact-analysis/SKILL.md
Commit: c6b2416

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