skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
terrylica/cc-skills79 installs

impact

Blast radius analysis via GitNexus CLI (gitnexus). CLI ONLY - NO MCP server exists, never use readMcpResource with gitnexus://.

How do I install this agent skill?

npx skills add https://github.com/terrylica/cc-skills --skill impact
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill facilitates codebase impact analysis using the gitnexus CLI. It features a self-evolution mechanism where the agent is instructed to autonomously update the skill's instructions. A risk surface for indirect prompt injection was identified because the skill processes untrusted repository content and possesses the capability to modify its own instruction file without adequate sanitization or boundary markers.

  • Socketwarn

    1 alert: gptAnomaly

  • Snykpass

    Risk: LOW · No issues

  • Runlayerpass

    1 file scanned · No issues

What does this agent skill do?

GitNexus Impact Analysis

CLI ONLY — no MCP server exists. Never use readMcpResource with gitnexus:// URIs.

Analyze the blast radius of changing a symbol — who calls it, what processes it participates in, and what tests cover it.

Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.

When to Use

  • Before modifying a function with many callers
  • "What breaks if I change X?"
  • "Is it safe to modify Y?"
  • "What's the blast radius of changing Z?"

Workflow

Step 0: Pre-flight — Ensure CLI Is Callable

The gitnexus binary is installed via npm/mise. The mise shim may fail if node isn't active in the current project. Run this pre-flight before any gitnexus command:

# Test if gitnexus is actually callable (not just a broken shim)
gitnexus --version 2>/dev/null || mise use node@25.8.0

All commands below run from the repo root. If multiple repos are indexed in the workspace, add --repo <repo-name> to specify the target. Otherwise --repo is optional.

Step 1: Auto-Reindex If Stale

gitnexus status

If stale (indexed commit ≠ HEAD), automatically reindex before proceeding — do not ask the user:

gitnexus analyze

Then re-check status to confirm index is current.

Step 2: Upstream Blast Radius

gitnexus impact "<symbol>" --depth 3

This shows everything that depends on the symbol (callers, transitive callers up to depth 3).

If multiple candidates are returned, disambiguate:

gitnexus impact "<symbol>" --uid "<full-uid>" --depth 3
# or
gitnexus impact "<symbol>" --file "<file-path>" --depth 3

Step 3: Downstream Dependencies (Optional)

gitnexus impact "<symbol>" --direction downstream --depth 3

Shows what the symbol depends on — useful for understanding if dependencies might change.

Step 4: Test Coverage

gitnexus impact "<symbol>" --include-tests

Shows which test files exercise this symbol.

Step 5: Risk Assessment

Based on the number of direct dependents:

DependentsRisk LevelRecommendation
< 5LOWSafe to modify with basic testing
5–20MEDIUMReview all callers, run related tests
20–50HIGHConsider backward-compatible API, extensive testing
50+CRITICALNeeds deprecation strategy, phased migration

Step 6: Structured Report

Present:

  • Risk level with dependent count
  • Top affected processes — execution flows that include this symbol
  • Direct callers — functions/methods that call this directly
  • Test coverage — tests that exercise this symbol (or gaps)
  • Recommendation — safe to modify, needs tests, needs migration plan

Example

User: "What breaks if I change RangeBarProcessor?"

gitnexus impact "RangeBarProcessor" --depth 3
gitnexus impact "RangeBarProcessor" --include-tests

Output: "CRITICAL risk — 73 dependents across 12 processes. 8 test files cover it. Recommend backward-compatible changes only."

Post-Execution Reflection

After this skill completes, reflect before closing the task:

  1. Locate yourself. — Find this SKILL.md's canonical path before editing.
  2. What failed? — Fix the instruction that caused it.
  3. What worked better than expected? — Promote to recommended practice.
  4. What drifted? — Fix any script, reference, or dependency that no longer matches reality.
  5. Log it. — Evolution-log entry with trigger, fix, and evidence.

Do NOT defer. The next invocation inherits whatever you leave behind.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/terrylica/cc-skills/impact">View impact on skillZs</a>