codemap-export

Included with Lifetime

$97 forever

Use to export the codemap as machine-readable JSON for downstream tooling. Same data as /codemap, different format. "Export the codemap", "give me the codemap as JSON".

General

What this skill does


# codemap-export

Machine-readable codemap. JSON output. Same data as `/codemap` text rendering, different format.

## Schema

```typescript
interface CodemapExport {
  version: '1';
  generatedAt: string;          // ISO 8601
  repo: { name: string; root: string; commit?: string };
  modules: Array<{
    name: string;
    path: string;
    loc: number;
    coverage?: { lines: number; branches: number; functions: number };
    lastTouched?: string;       // ISO 8601
    publicApi: string[];
    importsFrom: string[];      // module names
    importedBy: string[];
    externalDeps: string[];
    confidence: 'high' | 'med' | 'low';
    confidenceReason?: string;
  }>;
  graph: Array<{ from: string; to: string; weight?: number }>;
  hotspots: Array<{ module: string; reason: string }>;
}
```

## Method

1. Run `/codemap` internally to gather signals.
2. Serialise to the schema above.
3. Write to `codemap.json` (default) or path supplied.
4. Optionally pretty-print.

## Output

JSON file at the chosen path. Stdout summary:

```
Wrote codemap.json
Modules:    5
Edges:      8
Hotspots:   0
Size:       3.2 KB
```

## Rules

- **Schema versioned** — `"version": "1"`. Future changes bump.
- **Stable field names** — downstream consumers depend on them.
- **Optional fields are explicit.** Don't conflate "missing" with "empty".
- **No prose.** This is data, not narrative.

## Anti-patterns

- Adding fields without bumping schema version
- Including LLM-generated commentary in the export
- Inconsistent module naming between graph edges and module list

## When NOT to use

- Human reading — use `/codemap` (text/markdown)
- Tiny repo — manual JSON faster
- Tool-specific format requested (e.g. dependency-cruiser) — use that tool

## Subagent dispatch

- Same as `/codemap` — chain it

## Value over native CC

CC won't naturally produce a stable, versioned, machine-readable schema for codebase metadata. The schema IS the value — feeds dashboards, drift monitors, CI checks.

Files: 1

Size: 2.2 KB

Complexity: 5/100

Category: General

Source: https://github.com/ialameh/sift-coder/tree/main/skills/docs/codemap-export

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts