How do I install the Cgc Usage skill?

Run npx skillmds@latest add ceilf6/cgc-usage in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cgc Usage safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cgc Usage?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cgc Usage free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cgc Usage?

ceilf6 (@ceilf6) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cgc Usage by ceilf6 — Agent Skill

Name: Cgc Usage
Author: ceilf6

Cgc Usage

Use for dead code detection, cyclomatic complexity analysis, code graph visualization, or cross-validating GitNexus caller/callee results. Examples: 'find dead code', 'which functions are too complex', 'visualize the call graph', 'cross-check callers'

ceilf6 7139631 2.4 KB Updated Sep 17, 2026

File contents

CodeGraphContext — Usage Guide

When to Use

"Find unused functions / dead code"
"Which functions are too complex?"
"Show me the call graph for X"
"Visualize class hierarchy"
"Cross-validate GitNexus callers with another source"

Workflow

Dead Code Detection

codegraphcontext analyze dead-code

Returns functions, classes, and methods with zero incoming references. Review results carefully — entry points (main, handlers, exports) will appear as "dead" since nothing calls them internally.

Complexity Analysis

codegraphcontext analyze complexity --threshold 10

Returns functions with cyclomatic complexity above the threshold. Higher values indicate more branching paths and harder-to-test code.

Visualization

# Visualize call graph for a specific function
codegraphcontext analyze calls myFunction --viz

# Visualize class inheritance tree
codegraphcontext analyze tree MyClass --viz

# Find and visualize symbols matching a pattern
codegraphcontext find pattern "Auth" --viz

Opens an interactive HTML graph in the browser.

Cross-Validation with GitNexus

When you want to verify GitNexus caller/callee results:

1. gitnexus_context({name: "targetSymbol"})     → GitNexus callers/callees
2. codegraphcontext analyze calls targetSymbol   → CGC callers/callees
3. Compare results — differences may indicate:
   - Stale index on one side (re-index)
   - Dynamic/indirect calls one tool catches but not the other
   - Different analysis depth or confidence thresholds

Index Management

# Full re-index
codegraphcontext index .

# Start live file watcher (auto-reindex on changes)
codegraphcontext watch .

# MCP server (for AI assistant integration)
codegraphcontext mcp start

Checklist

- [ ] Identify the task: dead code / complexity / visualization / cross-validation
- [ ] Run the appropriate CGC command
- [ ] For dead code: filter out known entry points before reporting
- [ ] For complexity: suggest refactoring for functions above threshold
- [ ] For visualization: open HTML in browser, confirm it renders
- [ ] For cross-validation: compare with GitNexus results, explain differences

---name: cgc-usagedescription: Use for dead code detection, cyclomatic complexity analysis, code graph visualization, or cross-validating GitNexus caller/callee results. Examples: 'find dead code', 'which functions are too complex', 'visualize the call graph', 'cross-check callers'---# CodeGraphContext — Usage Guide## When to Use- "Find unused functions / dead code"- "Which functions are too complex?"- "Show me the call graph for X"- "Visualize class hierarchy"- "Cross-validate GitNexus callers with another source"## Workflow### Dead Code Detection```bashcodegraphcontext analyze dead-code```Returns functions, classes, and methods with zero incoming references. Review results carefully — entry points (main, handlers, exports) will appear as "dead" since nothing calls them internally.### Complexity Analysis```bashcodegraphcontext analyze complexity --threshold 10```Returns functions with cyclomatic complexity above the threshold. Higher values indicate more branching paths and harder-to-test code.### Visualization```bash# Visualize call graph for a specific functioncodegraphcontext analyze calls myFunction --viz# Visualize class inheritance treecodegraphcontext analyze tree MyClass --viz# Find and visualize symbols matching a patterncodegraphcontext find pattern "Auth" --viz```Opens an interactive HTML graph in the browser.### Cross-Validation with GitNexusWhen you want to verify GitNexus caller/callee results:```1. gitnexus_context({name: "targetSymbol"}) → GitNexus callers/callees2. codegraphcontext analyze calls targetSymbol → CGC callers/callees3. Compare results — differences may indicate: - Stale index on one side (re-index) - Dynamic/indirect calls one tool catches but not the other - Different analysis depth or confidence thresholds```## Index Management```bash# Full re-indexcodegraphcontext index .# Start live file watcher (auto-reindex on changes)codegraphcontext watch .# MCP server (for AI assistant integration)codegraphcontext mcp start```## Checklist```- [ ] Identify the task: dead code / complexity / visualization / cross-validation- [ ] Run the appropriate CGC command- [ ] For dead code: filter out known entry points before reporting- [ ] For complexity: suggest refactoring for functions above threshold- [ ] For visualization: open HTML in browser, confirm it renders- [ ] For cross-validation: compare with GitNexus results, explain differences```

Frequently asked questions